Hi, I need to know if someone with Athlon XP or Sempron CPU has also problems with Windows Developer Preview. Every time I run Services or EventViewer...etc the application crashes with the culprit being d3d10warp.dll.


I tested it in 3 PCs with different video cards and now I suspect is the CPU. (which lacks SSE2 instructions)

Originally Posted by vrosa

I dont think it's the CPU, at least there's no reference to SSE2 instructions in the official requirements.

1 gigahertz (GHz) or faster 32-bit (x86) or 64-bit (x64) processor
1 gigabyte (GB) RAM (32-bit) or 2 GB RAM (64-bit)
16 GB available hard disk space (32-bit) or 20 GB (64-bit)
DirectX 9 graphics device with WDDM 1.0 or higher driver
Taking advantage of touch input requires a screen that supports multi-touch
To run Metro style Apps, you need a screen resolution of 1024 X 768 or greater

Thanks vrosa. You are right about the requirements that's why I think it could be a bug. And is not the first time Microsoft makes this type of mistake.
Visual Studio 2010 RTM had a bug which any program or dll compiled with it would fail in a Athlon XP. (SSE2 instructions were always used even if the CPU didn't support them)
It was fixed in VS2010 SP1.

Originally Posted by CPJames

I have a AMD Sempron 3500+ CPU and it seems to run WDP okay. However, I haven't tried to run event viewer yet -I'll report back later what happens (since I'm on another computer at the moment).

Update

Event viewer works fine for me.

Thanks a lot for testing. Your processor is a Mobile Sempron, right? Those has SSE2 instructions so that's why it works fine.

I have tested with 2 more PCs, Athlon XP 3000+ and AMD Athlon64 3200+ and the result confirm my suspicions. The Athlon64 didn't crash because it has SSE2, the Athlon XP 3000+ crash because it lacks those instructions.

So after this I can confirm WDP doesn't work well with SocketA processors. (Athlon XP /Desktop Sempron)

Nice catch!

Doubly Confirmed, I just loaded WDP onto an old Athlon XP1800 system, which I know lacks SSE2.
I received an identical crash to what you described when trying to run both Services and Event Viewer.

Originally Posted by jygoro

Originally Posted by CPJames

I have a AMD Sempron 3500+ CPU and it seems to run WDP okay. However, I haven't tried to run event viewer yet -I'll report back later what happens (since I'm on another computer at the moment).

Update

Event viewer works fine for me.

Thanks a lot for testing. Your processor is a Mobile Sempron, right? Those has SSE2 instructions so that's why it works fine.

I have tested with 2 more PCs, Athlon XP 3000+ and AMD Athlon64 3200+ and the result confirm my suspicions. The Athlon64 didn't crash because it has SSE2, the Athlon XP 3000+ crash because it lacks those instructions.

So after this I can confirm WDP doesn't work well with SocketA processors. (Athlon XP /Desktop Sempron)

Yeh I have AMD Mobile Sempron Processor. Extract from Wikipedia regarding Sempron 3500+ model CPU's:

"Keene" (Socket S1, F2, 90 nm, Low power)

• All models support: MMX, SSE, SSE2, SSE3, Enhanced 3DNow!, NX bit, AMD64, PowerNow!
  

After so more research found out my CPU supports 64bit -only problem is I don't know if I could find all the 64bit drivers for my Dell Inspiron 1501.

Originally Posted by gdm40

Nice catch!

Doubly Confirmed, I just loaded WDP onto an old Athlon XP1800 system, which I know lacks SSE2.
I received an identical crash to what you described when trying to run both Services and Event Viewer.

Thanks a lot for testing! I hope they fix this because other than that issue Windows 8 runs beautifully on this PC.

Originally Posted by CPJames

Originally Posted by jygoro

Originally Posted by CPJames

I have a AMD Sempron 3500+ CPU and it seems to run WDP okay. However, I haven't tried to run event viewer yet -I'll report back later what happens (since I'm on another computer at the moment).

Update

Event viewer works fine for me.

Thanks a lot for testing. Your processor is a Mobile Sempron, right? Those has SSE2 instructions so that's why it works fine.

I have tested with 2 more PCs, Athlon XP 3000+ and AMD Athlon64 3200+ and the result confirm my suspicions. The Athlon64 didn't crash because it has SSE2, the Athlon XP 3000+ crash because it lacks those instructions.

So after this I can confirm WDP doesn't work well with SocketA processors. (Athlon XP /Desktop Sempron)

Yeh I have AMD Mobile Sempron Processor. Extract from Wikipedia regarding Sempron 3500+ model CPU's:

"Keene" (Socket S1, F2, 90 nm, Low power)

• All models support: MMX, SSE, SSE2, SSE3, Enhanced 3DNow!, NX bit, AMD64, PowerNow!
  

After so more research found out my CPU supports 64bit -only problem is I don't know if I could find all the 64bit drivers for my Dell Inspiron 1501.

1Gb of RAM? I think you should have at least 2Gb for WDP 64 bits.

Originally Posted by CPJames

Originally Posted by jygoro

Originally Posted by CPJames

I have a AMD Sempron 3500+ CPU and it seems to run WDP okay. However, I haven't tried to run event viewer yet -I'll report back later what happens (since I'm on another computer at the moment).

Update

Event viewer works fine for me.

Thanks a lot for testing. Your processor is a Mobile Sempron, right? Those has SSE2 instructions so that's why it works fine.

I have tested with 2 more PCs, Athlon XP 3000+ and AMD Athlon64 3200+ and the result confirm my suspicions. The Athlon64 didn't crash because it has SSE2, the Athlon XP 3000+ crash because it lacks those instructions.

So after this I can confirm WDP doesn't work well with SocketA processors. (Athlon XP /Desktop Sempron)

Yeh I have AMD Mobile Sempron Processor. Extract from Wikipedia regarding Sempron 3500+ model CPU's:

"Keene" (Socket S1, F2, 90 nm, Low power)

• All models support: MMX, SSE, SSE2, SSE3, Enhanced 3DNow!, NX bit, AMD64, PowerNow!
  

After so more research found out my CPU supports 64bit -only problem is I don't know if I could find all the 64bit drivers for my Dell Inspiron 1501.

I have a HP 5215us and it took me about 6 weeks to find all of the drivers for 64 bit. All you realy need to know is the chipsets being used on your computer and have a list writen down of the drivers you currently have. A great placle to look is Windows Update Catalog. Just google that and it will come up. its not the easiest place to find drivers but they are all there. Most of the pain services use a program that looks at this page and gets them from there.