VOGONS


First post, by computergeek92

User metadata
Rank Oldbie
Rank
Oldbie

I'm getting a blue screen when I try installing 2000 on my K6-2 IBM Aptiva. This error happens when I install to a hard drive attatched to my Promise ATA66 card. The hdd is a 120GB. When I install 2000 on a hdd using the onboard ide on the mobo, win2k installs just fine. But the mobo's bios only supports up to about 32gb hard drives. so the ATA66 card is the only way to use my 120Gb drive. The mobo is an Acer V70MA 98101-1. I recently upgraded the original K6-2 333. (95MHz fsb) I thought the non-standard 95mhz bus was causing the problem, so I put in a K6-2 450 (100mhz bus) and it did not prevent the BSOD. I put Windows 98 on this machine instead but the boot time is slow when installed on the 120GB hdd and before I installed the ATA66 drivers for Win98, I had serious OS stability issues. Ibms are flaky machines... 😜
Anyway, here is the exact error messege I recieved onscreen:

*** STOP: 0x0000000A <0x00000018,0x00000002,0x00000000,0x8042E6E9>
IRQL_NOT_LESS_OR_EQUAL

*** Address 8042E6E9 base at 8040000, DateStamp 3d366b8b - ntoskrnl.exe

Beginning dump of physical memory
Physical memory dump complete. Contact your system administrator or
technical support group.

Dedicated Windows 95 Aficionado for good reasons:
http://toastytech.com/evil/setup.html

Reply 1 of 5, by Nahkri

User metadata
Rank Member
Rank
Member

Have u tried partitioning the drive?and install the os to a smaller partition?

Reply 2 of 5, by GeorgeMan

User metadata
Rank Oldbie
Rank
Oldbie

I had IRQL_NOT_LESS_OR_EQUAL problems in the past on NT (basically XP).

When exactly this bsod appears? Right after installing 2k? When trying to boot after a successfull install? During install?
Try to format the HDD and install 2k with the HDD already attached to the controller.
You can also try to find an updated BIOS for that IBM, or even a beta or 3rd party one, that enables support for 128GB HDDs.

Acer Helios Neo 16 | i7-13700HX | 64G DDR5 | RTX 4070M | 32" AOC 75Hz 2K IPS + 17" DEC CRT 1024x768 @ 85Hz
Win11 + Virtualization => Emudeck @consoles | pcem @DOS~Win95 | Virtualbox @Win98SE & softGPU | VMware @2K&XP | ΕΧΟDΟS

Reply 3 of 5, by computergeek92

User metadata
Rank Oldbie
Rank
Oldbie
Nahkri wrote:

Have u tried partitioning the drive?and install the os to a smaller partition?

Yes I know how to install 2k. I partitioned and installed to a smaller 6GB partition for testing.

Last edited by computergeek92 on 2015-07-13, 19:45. Edited 1 time in total.

Dedicated Windows 95 Aficionado for good reasons:
http://toastytech.com/evil/setup.html

Reply 4 of 5, by computergeek92

User metadata
Rank Oldbie
Rank
Oldbie
GeorgeMan wrote:
I had IRQL_NOT_LESS_OR_EQUAL problems in the past on NT (basically XP). […]
Show full quote

I had IRQL_NOT_LESS_OR_EQUAL problems in the past on NT (basically XP).

When exactly this bsod appears? Right after installing 2k? When trying to boot after a successfull install? During install?
Try to format the HDD and install 2k with the HDD already attached to the controller.
You can also try to find an updated BIOS for that IBM, or even a beta or 3rd party one, that enables support for 128GB HDDs.

The BSOD appears after the first reboot during the win2k install when setup is "detecting and installing devices such as your keyboard and mouse"

The hard drive is attatched to the computer and I formatted and installed it like your would with any fully built PC. The promise ATA66 card is in the PCI slot and cabled to the 120GB drive.

I'm having a really hard time finding any BIOS update for the mobo. It looks like there were other model 2153 Aptivas with Intel, not AMD, chipsets. My model is the:

2153-E2C

S/N AF 23NZG

Dedicated Windows 95 Aficionado for good reasons:
http://toastytech.com/evil/setup.html

Reply 5 of 5, by ibm5155

User metadata
Rank Member
Rank
Member

Well it looks like my setup, unstable with windows 98 ( one interesting note, when it freeze during boot, the hdd light stays on, without flashing or turning off).
The only familiar thing between our systems is that we both are working with an hdd In compatibility mode...
On my case it could be fixed with a bios update, but for that I would need a new bios chip since its read only, and can only be erased by ultraviolet)