This Guy Says He's Running Crysis On Nt 3.51 On A 486????
Forum rules
Any off topic discussions should go in this forum. Post count is not increased by posting here.
Archive Access status is required to post in this forum. Find out how to get it
Any off topic discussions should go in this forum. Post count is not increased by posting here.
Archive Access status is required to post in this forum. Find out how to get it
This Guy Says He's Running Crysis On Nt 3.51 On A 486????
I'm running Crysis under windows NT 3.51 on a 486 (with 2GB virtual memory on a gigabyte I-RAM, a SATA card and a PCI-to-AGP adapter with a radeon 9800) and for convenience I hacked the explorer to use DOSSHELL instead http://www.reactos.org/forum/viewtopic. ... 4&start=15
- os2fan2
- Donator
- Posts: 1394
- Joined: Sun Dec 30, 2007 8:12 am
- Location: Brisbane, Queensland
- Contact:
You can run Win351 on very little RAM. The actual OS is only something like 30 MB, and it happily boots on a 486. I ran NT 4,0 in 20 MB on a 486DX66 (somewhat sluggishly).
With regard to the claim of RAM, 486 machines were typically made when ram-sticks cost lots of money. Machines with 32 MB, might be considered server class, the usual home fare when 486's ruled the earth was in the range of 4-32 MB. Many of the bioses were simply not equipped to handle this core.
Windows 3.1 could only handle 1 G: this is a limitation to the OS addressing. Windows 95 (an early pentium OS), had a natorious bug at 64 MB, and machines of this vintage had an OS/2 switch in BIOS. Some still do. [modern OS/2 systems have this set to NO].
It is pretty easy to set RUNWORKPLACE in these operating systems. I had Win95 using something like SOL.EXE as the shell. Windows 3.51 used a different PM layer to later versions. If you dual boot, this setting is in a text file in the Windows directory.
Wikipedia gives CRYSIS as requiring Windows XP or Vista with directx 9.0c. I am not sure if directx 9.0c will install on 3.51, since the OS has a lot of missing APIs. Some of the installs for games are set artificially high, so it is possible that were 9.0c installed, then it could run.
With regard to the claim of RAM, 486 machines were typically made when ram-sticks cost lots of money. Machines with 32 MB, might be considered server class, the usual home fare when 486's ruled the earth was in the range of 4-32 MB. Many of the bioses were simply not equipped to handle this core.
Windows 3.1 could only handle 1 G: this is a limitation to the OS addressing. Windows 95 (an early pentium OS), had a natorious bug at 64 MB, and machines of this vintage had an OS/2 switch in BIOS. Some still do. [modern OS/2 systems have this set to NO].
It is pretty easy to set RUNWORKPLACE in these operating systems. I had Win95 using something like SOL.EXE as the shell. Windows 3.51 used a different PM layer to later versions. If you dual boot, this setting is in a text file in the Windows directory.
Wikipedia gives CRYSIS as requiring Windows XP or Vista with directx 9.0c. I am not sure if directx 9.0c will install on 3.51, since the OS has a lot of missing APIs. Some of the installs for games are set artificially high, so it is possible that were 9.0c installed, then it could run.
- Rob Jansen
- Donator
- Posts: 5271
- Joined: Sat May 12, 2007 1:05 pm
- Location: The Collection Book
- Contact:
-
ppc_digger
- Donator
- Posts: 590
- Joined: Sat Aug 19, 2006 1:25 am
- Location: Israel
Actually, theoretically, the 486 can support the full 4 GB of address space. The 486 motherboards, on the other hand, are limited (although the first post says 2 GB of virtual memory, which doesn't depend on the motherboard). As for the other stuff, a SATA controller can work with appropriate drivers (which, if not compatible with NT 3.51, can be ported from Linux to the 3.51 driver API). As with the SATA drivers, the open source Radeon 9800 (which could be a PCI version, which has an onboard PCI-to-AGP bridge) driver could be ported (although with a lot of effort). Finally, DirectX 9 support can be implemented using Wine DLLs (again, ported).
So, while extremely difficult, running Crysis on NT 3.51 on a 486 with a Radeon 9800 is (at least theoretically) possible.
So, while extremely difficult, running Crysis on NT 3.51 on a 486 with a Radeon 9800 is (at least theoretically) possible.
While theoretically possible, assuming that the engine isn't compiled to use SSE or MMX exclusively, that looks a lot like a fakepost to me.
Let's sperg about hardware
E6410 - i5-560m, 8GB, WXGA+, NVS 3100M, Samsung SSD 830 128GB, WWAN, 9-cell, E-Port Plus Replicator
Desktop - i5-2500k (4.3 GHz TB), 8 GB, HD6950 2GB, 2x24" 1080p, Samsung SSD 830 128GB + 2 TB stripe, Xonar D2X
E6410 - i5-560m, 8GB, WXGA+, NVS 3100M, Samsung SSD 830 128GB, WWAN, 9-cell, E-Port Plus Replicator
Desktop - i5-2500k (4.3 GHz TB), 8 GB, HD6950 2GB, 2x24" 1080p, Samsung SSD 830 128GB + 2 TB stripe, Xonar D2X
-
ppc_digger
- Donator
- Posts: 590
- Joined: Sat Aug 19, 2006 1:25 am
- Location: Israel
SSE and MMX can both be emulated (early in the OSx86 project, someone wrote an SSE3 emulator). This guy said that Crisys works, not that it's playable. A few years ago, someone ran Panther on a 68k Mac (link). It worked, but it took a whole week to boot. Every Turing-complete computer can emulate another Turing-complete computer.longview wrote:While theoretically possible, assuming that the engine isn't compiled to use SSE or MMX exclusively, that looks a lot like a fakepost to me.
Running Crysis on NT 3.51 (which is much harder than running it on Windows 2000 on a 486, which is probably easily doable) will be harder than running Panther on a Centris, though.
- Vista Ultimate R2
- Posts: 2393
- Joined: Wed Aug 30, 2006 10:06 pm
Would Windows 2000 even work on a 486 though? - I know XP needs a Pentium to be able to boot. Running Crysis on NT 3.51 would be impossible, there's no DirectX at all let alone the required 9.0c for a start. Even Windows 2000 would be likely to be difficult, it depends whether the XP+ requirement is artificial and they just couldn't be bothered testing 2000 as no gamers use it any more, or whether it actually uses things found only in XP and newer versions.ppc_digger wrote:Running Crysis on NT 3.51 (which is much harder than running it on Windows 2000 on a 486, which is probably easily doable) will be harder than running Panther on a Centris, though.
-
ppc_digger
- Donator
- Posts: 590
- Joined: Sat Aug 19, 2006 1:25 am
- Location: Israel
I haven't found anything regarding Windows 2000, but XP can't run on a 486 because it requires the CPUID (which is supported on later 486s) and the CMPXCHG8B (which is only available since the Pentium) instructions. I believe the last can be emulated with an appropriate Windows driver (unless Windows needs to use it before all the drivers are loaded. In that case, the kernel would need to be patched).Vista Ultimate R2 wrote:Would Windows 2000 even work on a 486 though? - I know XP needs a Pentium to be able to boot. Running Crysis on NT 3.51 would be impossible, there's no DirectX at all let alone the required 9.0c for a start. Even Windows 2000 would be likely to be difficult, it depends whether the XP+ requirement is artificial and they just couldn't be bothered testing 2000 as no gamers use it any more, or whether it actually uses things found only in XP and newer versions.ppc_digger wrote:Running Crysis on NT 3.51 (which is much harder than running it on Windows 2000 on a 486, which is probably easily doable) will be harder than running Panther on a Centris, though.
Also, as I said before, running Crysis could be possible using Wine DLLs, which emulate DirectX on top of OpenGL (which is available for NT 3.51; I don't know which version, though).
Look at this string from SetupLDR.
Yet this string conflicts:
Code: Select all
Windows requires an 80486 or later processor.
Code: Select all
Windows requires certain processor features that are not available
on the processor in this computer. Specifically, Windows requires
the following instructions.
CPUID
CMPXCHG8B
-
ppc_digger
- Donator
- Posts: 590
- Joined: Sat Aug 19, 2006 1:25 am
- Location: Israel
Maybe that requirement was added later in the development process, and setupldr wasn't updated.Windows OCManage wrote:Look at this string from SetupLDR.
Yet this string conflicts:Code: Select all
Windows requires an 80486 or later processor.
Code: Select all
Windows requires certain processor features that are not available on the processor in this computer. Specifically, Windows requires the following instructions. CPUID CMPXCHG8B