Checklist
What happened?
Well i installed Sleek / Nite version of WIndows 98 into Vmware.
For some reason some wrong Network card is detected forced.
I read it description that Ndis2 driver is used for Broadcom 57xx because original Windows 32 bit drivers sucks, but nothing about AMD.
Main problem with Ndis driver, besides that is probably much slower is that it does not support all features of full 32 bit driver probably. I had the same problem on the physical machines with Realtek NIC, when i forced use of Ndis2 driver. Blue screen code if my memory serves is the same on this virtual machine and physical one:
Every time when i enable Filesharing with i got bluescreen after login and ping is working, but access to modern Windows network shares is not. I have downgraded WIndows 10 Nas security and all my machine to Samba 1, enabled a bit more gpedit compatibility policies on targer machines and access from WIndows 98 machine to all up to Windows 10 shares is working fine.
In Windows 98 i have some sometimes add this registry key:
_REGEDIT4
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa]
"LMCompatibility"=dword:00000003
"LmCompatibilityLevel"=dword:00000001_
Vmwares default for Windows 98 is AMD PCNet-Fast III Ethernet Adapter (Am79C973), i not have issues this it.
I looked into drivers library but it not found it, im not sure how quickly search all Drivers packs, or if they are installed all supported devices should be already in Hardware devices database.
With stock Windows 98 driver is available auto installed during OS installation.
Target Motherboard, CPU and RAM
Vmware Workstation 25 default
Target GPU and Sound card(s)
Vmware Workstation 25 default
Target Storage Devices
Good news is that NVME, IDE and Sata are working, after switching to them after install worked well.
I even tried to force EFI boot, it started, but ended up with kernel panic, i reported by to CSMWrap github.
There could be handy to tell use that its actually possible only use MBR for OS drive, i prepared GPT, because of EFI,
but found out later that MBR is required by installer and recommended (not required) by CSMWrap. So its a bit hybrid strange setup UEFI boot from MBR disk with EFI folder.
Boot method
Original boot loader.
Checklist
Skip legacy non-PnP hardware detection phaseto[OFF]and the issue still occurs.[OFF]and the issue still occurs.What happened?
Well i installed Sleek / Nite version of WIndows 98 into Vmware.
For some reason some wrong Network card is detected forced.
I read it description that Ndis2 driver is used for Broadcom 57xx because original Windows 32 bit drivers sucks, but nothing about AMD.
Main problem with Ndis driver, besides that is probably much slower is that it does not support all features of full 32 bit driver probably. I had the same problem on the physical machines with Realtek NIC, when i forced use of Ndis2 driver. Blue screen code if my memory serves is the same on this virtual machine and physical one:
Every time when i enable Filesharing with i got bluescreen after login and ping is working, but access to modern Windows network shares is not. I have downgraded WIndows 10 Nas security and all my machine to Samba 1, enabled a bit more gpedit compatibility policies on targer machines and access from WIndows 98 machine to all up to Windows 10 shares is working fine.
In Windows 98 i have some sometimes add this registry key:
_REGEDIT4
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa]
"LMCompatibility"=dword:00000003
"LmCompatibilityLevel"=dword:00000001_
Vmwares default for Windows 98 is AMD PCNet-Fast III Ethernet Adapter (Am79C973), i not have issues this it.
I looked into drivers library but it not found it, im not sure how quickly search all Drivers packs, or if they are installed all supported devices should be already in Hardware devices database.
With stock Windows 98 driver is available auto installed during OS installation.
Target Motherboard, CPU and RAM
Vmware Workstation 25 default
Target GPU and Sound card(s)
Vmware Workstation 25 default
Target Storage Devices
Good news is that NVME, IDE and Sata are working, after switching to them after install worked well.
I even tried to force EFI boot, it started, but ended up with kernel panic, i reported by to CSMWrap github.
There could be handy to tell use that its actually possible only use MBR for OS drive, i prepared GPT, because of EFI,
but found out later that MBR is required by installer and recommended (not required) by CSMWrap. So its a bit hybrid strange setup UEFI boot from MBR disk with EFI folder.
Boot method
Original boot loader.