Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Advanced Micro Devices - Moderated (AMD) -- Ignore unavailable to you. Want to Upgrade?

To: Petz who wrote (69042)	1/26/2002 3:22:12 AM
From: kapkan4u	Read Replies (2) \| Respond to of 275872

You can't say that Hammer executes 32-bit software in 64-bit chunks, just like you couldn't say that i386 was executing 16-bit software in 32-bit chunks. The 64-bit registers are involved in computations but the upper bits are unused and inaccessible, so there are absolutely no 64-bit chunks anywhere when running 32-bit codes. Kap

To: Petz who wrote (69042)	1/26/2002 6:12:45 AM
From: dumbmoney	Respond to of 275872

help me recall this. Windows 386 and Windows 3.1 really only used the "virtual 8086" mode of the 386/486/Pentium. Correct? The statement is ambiguous. Windows programs didn't run in 32-bit mode. They also didn't run in V86 mode; that was for DOS programs. IBM's OS/2 beat Windows 95 to market and had a true 32 bit API, but I don't think it ever had nearly as many applications written for it as Linux does now. Not sure about that. OS/2 had pretty broad support, and of course it ran Windows apps also. The thing about Linux is that it is unstoppable, unlike commercial software. They is no company that can pull the plug on it, so it's here to stay (or as long as it fills a need). Linux is Microsoft's #1 competitor, no doubt about that.

To: Petz who wrote (69042)	1/26/2002 10:27:24 AM
From: Elmer	Respond to of 275872

help me recall this. Windows 386 and Windows 3.1 really only used the "virtual 8086" mode of the 386/486/Pentium. Correct? Windows 3.1 ran Dos applications in V86 mode with each session having it's own address space. It used preemptive multi tasking between them(V86) and a single 286 type 24bit address space where all windows applications ran in cooperative multitasking mode sharing a single address space. So windows used cooperative multitasking between windows apps and preemptive multitasking between windows and each V86 session. Windows could hang between windows applications but the V86 sessions were unaffected (in theory). EP

To: Petz who wrote (69042)	1/26/2002 10:49:22 PM
From: dale_laroy	Read Replies (1) \| Respond to of 275872

>help me recall this. Windows 386 and Windows 3.1 really only used the "virtual 8086" mode of the 386/486/Pentium. Correct? IBM's OS/2 beat Windows 95 to market and had a true 32 bit API, but I don't think it ever had nearly as many applications written for it as Linux does now.< Windows 2.0 was 286 mode only. Beginning with Windows 3.0, while the GUI itself was written to execute in 286 mode, 32-bit applications would run on 386/486/Pentium processors thunking down to 286 mode for Windows 3.x calls.