VOGONS


First post, by superfury

User metadata
Rank l33t++
Rank
l33t++

Anyone knows what Windows 95 is doing during this step in the BOOTLOG.TXT file? This is the last thing that's logged by the boot process before it throws a BSOD(at segment 117, so a program/driver in User mode is executing).

Author of the UniPCemu emulator.
UniPCemu Git repository
UniPCemu for Android, Windows, PSP, Vita and Switch on itch.io

Reply 1 of 3, by superfury

User metadata
Rank l33t++
Rank
l33t++

Hmmmm... Interestingly enough, at https://www.google.com/amp/s/www.techsu ... ml%3famp=1 , the Initializing KERNEL is followed by:

LoadStart = system.drv

on the next row. Does that mean that the issue is somewhere within that kernel initialization? Or is it somewhere loading the system.drv file somehow?

Author of the UniPCemu emulator.
UniPCemu Git repository
UniPCemu for Android, Windows, PSP, Vita and Switch on itch.io

Reply 2 of 3, by retardware

User metadata
Rank Oldbie
Rank
Oldbie

Your Windows 4 installation is probably broken (might be just a bad reg setting or driver).

Set BootGUI=0 in MSDOS.SYS and start windows by hand.

Reply 3 of 3, by superfury

User metadata
Rank l33t++
Rank
l33t++

Well, afaik Windows itself(on the emulated harddisk) isn't the issue. There's some CPU emulation issue in UniPCemu that's causing it. It's booting fine when loading the disk image in the Bochs emulator.

But afaik the CPU instructions have all been tested and verified(except some remaining Protected Mode systems instructions) in the test386.asm CPU testsuite.

The only unverified instructions that are left untested in the testsuite are the instructions that have to do with protected mode itself.

I've reinstalled Windows 95 many times when finding CPU bugs, but that error (BSOD in safe mode) won't go away? Normal mode boot is even worse, loading what seems to be a ATA(PI) driver(esdi_506.pdr) twice, crashing when initing the second one.

[00000564] Initing hsflop.pdr
[00000569] Init Success hsflop.pdr
[0000056B] Initing esdi_506.pdr
[00000586] Init Success esdi_506.pdr
[someothernumberhere] Initing esdi_506.pdr

The ATA(PI) driver crash results in a black screen with a message that Windows failed to load(or something comparible) and reinstall Windows if it persists. Nothing more is printed on the screen.
Afaik it isn't supposed to init it twice? Or is that because of two IDE controllers(Primary Master/Slave are harddisks, Secondary Master/Slave are ATAPI CD-ROM drives)?

Author of the UniPCemu emulator.
UniPCemu Git repository
UniPCemu for Android, Windows, PSP, Vita and Switch on itch.io