[Hazaanko]

awwww, poor mac os classic (9)

[phreak]

x64 was NOT a good version of windows.  It was a hackjob OS that had way more problems than XP ever did.  The 32bit program support was mediocre at best, and the driver support was absolutely deplorable.  To think I ran that garbage OS for six months, getting BSODs and random restarts before I realized it was the fault of XP64 and not my hardware still escapes my mind.  I shudder at the idea of installing it for anybody, and the experience pushed me away from future 64bit OSs.  Seriously, it was god awful.

Then you're running a different version for me since it's been smooth sailing.

[colecampbell666]

Once 64-bit becomes standard it will be fine. I'm sure the same thing happened with 32-bit, and sixteen. Is Vista 64 any better?

There's a difference in the industry now.  When the shift from 16 to 32 was made, the market wasn't nearly the size it is now.  Basically everyone who upgraded knew what they were doing, and things were much less complex.

When was the shift?

[Scuddie]

Then you're running a different version for me since it's been smooth sailing.

Many people running Windows ME said the very same thing.  For those it worked for, it worked wonderfully.  Not the case with everyone else.

When was the shift?

In the Microsoft arena, Win95 was the first to utilize 32bit instruction code, but a true 32bit OS didn't appear until NT 4.0.  Windows 3.1 and NT 3.5 had page swapping options for logical 32bit memory addressing, but the kernel was primarily 16bit.

[jr2]

Ummm... what about Windows for Workgroups 3.11?  (not to be confused with Windows 3.11).

[Scuddie]

WIN32s was not supported in WFW 3.11 until a service pack was released.  IIRC, it was available on NT3.5 before WFW 3.11.

But still, it was a hackjob.  WFW was not natively designed to handle 32bit instruction code.

[jr2]

And this means...?  (Linky to Yale site.)

EDIT: nvm

The presence of some 32-bit internal VxD components does not change the external program interface. The same WIN32S package that installs in Windows 3.1 can also be installed in WFWG 3.11. As before, all 32-bit requests are simply translated to 16-bit requests before execution.

[Nuke]

sometimes i run riscos 3 in a virtual machine so i can play arc elite

[Scuddie]

And this means...?  (Linky to Yale site.)

EDIT: nvm

The presence of some 32-bit internal VxD components does not change the external program interface. The same WIN32S package that installs in Windows 3.1 can also be installed in WFWG 3.11. As before, all 32-bit requests are simply translated to 16-bit requests before execution.

/me checks his sources...

Well, I'll be damned.  I had no idea WFW could use the same WIN32s package that worked for Windows 3.1.  Not much I can do about that now, though .

[jr2]

Sure you can..

Virtual pc.  *cough* I have... sources.    Erm.  That's odd!  Umm, I think so, too.  Seriously.  Wow.  Arg!  Right, now what?  Extraordinary! ... Can't quite figure this out.  On the other hand.  Methinks I'm done with this paragraph now. 

* jr2 runs from admins.