Windows 95 bootlog Initializing KERNEL

Emulation of old PCs, PC hardware, or PC peripherals.

Windows 95 bootlog Initializing KERNEL

Postby superfury » 2019-3-04 @ 20:10

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).
superfury
l33t
 
Posts: 3230
Joined: 2014-3-08 @ 11:25
Location: Netherlands

Re: Windows 95 bootlog Initializing KERNEL

Postby superfury » 2019-3-19 @ 22:37

Hmmmm... Interestingly enough, at https://www.google.com/amp/s/www.techsu ... ml%3famp=1 , the Initializing KERNEL is followed by:
Code: Select all
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?
superfury
l33t
 
Posts: 3230
Joined: 2014-3-08 @ 11:25
Location: Netherlands

Re: Windows 95 bootlog Initializing KERNEL

Postby retardware » 2019-3-19 @ 22:41

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.
retardware
Oldbie
 
Posts: 642
Joined: 2019-1-30 @ 02:00

Re: Windows 95 bootlog Initializing KERNEL

Postby superfury » 2019-3-19 @ 23:35

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.
Code: Select all
[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)?
superfury
l33t
 
Posts: 3230
Joined: 2014-3-08 @ 11:25
Location: Netherlands


Return to PC Emulation

Who is online

Users browsing this forum: No registered users and 2 guests