ruthan

Thx for info. I have tried fix above good it that it booted after installation and its compatible with other Rloew patches which are already editing this file.. other good thing is that it be installed on the fly. My machine above seems to affected by other bugs, but this not helped to solve any conflict or enable some address ranges. The last thing which is still open is IRQ Steering settings on the PCI bus component.. So far i did not find some good info which settings are better for which scenario - its default setting. If IRQ for Realmode or Protected more better for Win9x.. i never even know that there to seperate data sources for it.. It make some Bios IRQ settings maybe even invalid.. because logic imply that at least one data source is different. I understand correctly - Windows 9x are running in protected mode.. i not so sure how its possible that i can use Network card driver which are reporting Real mode how to it works together but ok. And ok if Windows 9x are running in protected mode, why PCI BUS IRQ Streering default value is Get IRQ Table from Real mode ACPI. I there so SW which can print out.. All ACPI tables - for old and new OSes? Or how too new versions of them are crippled by OS Windows 9x?

Well question is you somehow force configuration which i not available in Device manager or not. I can fiddle with IRQs in bios - but im not sure it will also change address ranges what is usually bigger problem, but could even break some modern OSes (Win2000 + XP) on the same HW. Yeah basic trick on lots of machine is replace whatever its actually named by PCI bus device to actually detect HW. I also have experience that clean install is not bad with resource management usually and if fiddle with them later, its often get worse and im unable to comeback. Im also to 100% sure if some resource overlay is actually problem, is its just some missing driver, which are supposed to use memory range of some master component. WFT something like Erunt for NT+ for saving registry backup would quite nice, i looked at Win9x registry regedit option there is registry backup option, but im not sure if could be started during machine boot and much time it would take. Or maybe i can do it right after boot by Start up item. Windows 98 has sometimes some registry autorecovery, but it often restore some ancient backup and im not even sure if i can cancel or turn it off. Another icing on the Win9x resource take is Windows protection error, after some resources fiddling.. if my memory serves its often impossible to recover from such state - or not without some not easy magic, like System.ini editing or start step by step loading confirmation. Im not really sure what is causing Windows protection errors.

Introduction analysis: I wonder, is there some advanced tricks how to solve Windows 9x resource conflicts? Is there some explanation, why these conflicts are in Windows 9x, but not it more moderns OSes, Linux or NT? I rarely met such problem in Dos, and often solution was - change card slot (problem is that on board devices is such trick not possible.), device IRQ if it available by device driver, or changing slots, device IRQs directly in the bios - if it was available. Where is exactly the problem? I actually never was some details info about, i only knew that by some PC standard there is only few free IRQ to use.. and more modern MBs not added much more new IRQ to use, probably because of backwards compatibility. Address range conflicts seems strange, there should be enough memory ranges to use to avoid conflicts, but its happening. My guesses are: a) Bios setting up something worse and Win9x just reuse its values and more modern OSes are adjusting setting on its own and automatically are solving conflings.. b) More modern OSes are able to handle 2 or more devices which are using the same address range and are able to switch address ranges automatically c) More different OSes are reading Bios data differently - ACPI, but if im not wrong Windows 9x could use ACPI too.. but if my memory serves there are some ACPI versions, im not sure if they are backwards compatible or if minimal version supported by individual OS, is available, what if happen.. Im not sure if some chipset drivers could adjust device resources in Win9x, or not. What i found online is that modern OSes are simply did better job of handling resources (avaible through ACPI + PnP) and are able to Bios data and adjust it to prevent conflicts, are somehow able to call devices a better way, by using HAL - hardware abstraction layer and disabling to call devices addresses directly - but it found sort of imply that such solution has to be much slower. I wonder i maybe someone could improve Windows 98 kernel to handle these things better as more modern OSes? Problem solving: What i was able to do in Win9x, was simply change resource values for some conflicting devices from some predefined values.. or through selection from a few prebacked values by disabling automatic configuration and in some cases i had to boot in Safe mode to do it. Problem is that often simply are not any available value except already used one and i dunno how to solve it. For example a see that the small part of address range of some device is used by other device. Question is, are there some additional tricks and tools to fix such problem? Its possible to change address range by some regedit tweaking etc? On some machine, when is possible to set some IRQ related settings on the PCI bus component, but i dont really know that should be best for my case - what is exactly IRQ steering.. and what difference is between using Hardware and BIos mode - what is MS specification table.. what uis PCIBIOS 2.1.. Could i ose Protected mode pcibios call for WIndows 9x (i read that its running in Realmode and Protected mode is used by more modern OSes)? , there is some example: - 0 additional cards added, all date are based on on board devices. Other interesting thing is that device conflict is often visible only on 1 device in case that 2 devices are conflicting. As faik as i unterstand Windows 9x are trying to make at least one of two conflicting devices running and other is disabled.. but still some other problem icon for conflicting device is currently running would be nice. These are some unsolvable problems with my Power Edge 1950 machine, which I'm currently setup.

I spend a quite a lot of time in the search for NT4 drivers for Broadcom NetXreme 5708 PCI-E cards.. I have classic not enough PCI-E / PCI slots problem, so i cant simply replace it. There as usually some drivers for more modern Windows which has false description claims about supporting - NT4 it their description on some driver download sites, but after downloading in real readme NT4 arent in the list of supported OS. I have tried some Windows 2000 drivers, but they are not working. So the last chance is try to ask here, because perhaps someone here has driver for it.. or has better driver google fu.. I have found and have on other machine working driver for previous generation Broadcom NetXtreme I - 5703 card.. (these are supported: and driver which is working with Broadcom 5721. I have also tried to modify NT4 driver for 5703 by adding HardwareIDs of 5708 to it - its 164C at the end, but NT4 drivers *.inf which i found seems much more complex than other *.inf, so my edit probably not worked, because when i tried to add it.. Device name was detected with wrong name (or maybe it is using generic one until extract card is detected).. but Maybe some has better *.inf modding skills. Others these cards has nice support of Everything from Dos to modern Windows, except NT4 and Windows 98 (but i already made Ndis2 dos driver working there).

Yeah im used to do it too, but its sort of the last resort it has some problem: - I usually migrating too old Oses to too modern machines, but hardware is not really similar because - but i never tried VirtualBox 4 - but it would need to install Virtual machine probably from the old machine too - What is newest OS supported by Virtualbox 4 - WinXP? - Qemu has i im not wrong much broader emulating HW options, but i never was friends its command line hell settings - GUI frontends for Windows where allways outdated and not great.. and even on Linux its problematic, especially KVM GPu passthrough with Qemu was allways hell.. Lastime when i tried it, i run into some App rights admin level issues.. because some new Linux xserver changes - its always moving target, when you are not using Linux on the daily basis.. - better options seems to be 86box -PCem successor emulation - could be can set up anything from 8086 to Pentium III (it could be too old) - partition is never issue, because there are is always some compatible tool from modern OS, or from BootCD - i have quite big collection of these on the Ventoy USB - ISO loader tool - For modern OS - Win2000+ - im using P2P HW Adjust tools - mostly from Paragon. So far i did not found such tool Windows 98 and NT4, it became a thing probably too late for these to support Im used to use it in the XP era.. Microsoft even had some tool called Sysprep for it, P2P tools above are probably based on it, but i never found some good and easy to implement tutorial for it, it always seemed a awkward.. BTW what is exactly Registry key to delete for Windows 98 or NT4? i have in some notes this: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum but its probably for WinXP.. There is also problem, you have to remove reg keys before making image, or do it through loading hive and i wrote.. so far i did not found tool to load Win9x offline.. NT4 have some different registry structure, but seems loading hive is possible. I read that is maybe possible to edit Win98 registry through some MS-DOS 7 tool command line tool, but i never tried it, it would be handy.

Ok i have tried all normal things like remote desktop FTP, access to Windows 98 share from modern Windows (10) all worked, but the most important thing - access from Windows 98 to Win 10 does not work.. I may have some mess with User accounts- ater account recreation / renaming, because unattended install or l etc, but i doubt it.. I simply get bluescreen when i add these keys to Registry to Win98: REGEDIT4 [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa] "LMCompatibility"=dword:00000003 "LmCompatibilityLevel"=dword:00000001 - i proven it with other machines that works for Win98 access to Win10 (After NTML version lowering it Windows 10).. - When i select cancel on the logon screen instead for network password login, i get not bluescreen.. I had tried to create entirely new user - but its the same.. Other someone could be able to tell from bluescreen text, its its networking related (VNETUP - looks very like it, press to continue freeze and N or Y settings is not wokring - maybe because of USB keyboard).. its some kernel / update mess, bluescreen text is: Invalid VxD dynamic link call from VREDIR(01) + 000071BE to device "VNETUP", service 8. Your Windows configuration is invalid. Run the Windows Setup program again to correct this problem. To continue running Windows press Y, to continue to run Windows without this problem press N. If you continue system may be unstable. Question is could Win10 filesharing works with Windows 98 - 16 bit drivers? Its ancient, but yeah its working from Win10 to Win98.. And if my memory servers for MS-DOS too there are would be probably the same 16 bit driver too.. - im not sure how NTML collaborating Windows 16 bit NDIS2 driver, maybe you need higher version for it. Other option is that i need some unofficial networking patch for it etc.. I dont really remember which packages installed on my machines where, it is working, so far it not verified it from the scratch.. There are some contradicting tutorials how to make Windows 98 to Windows 10 access working (some hinting to delete all LM** keys).. I have installed SSH server on my Windows 10 machines, so i can use WinSCP or Total COmmander plugins, but this its not as good as vanilla Windows network folder access.. What is interesting this settings is working even when Windows 98 filesharing network component is not installed, but maybe this component is only need for access to Windows 98 share (Description seems to imply it) - i never had much interesting in networking details. BTW 7 years ago i did detailed MS-DOS to Win10 networking analysis guide, it could be handy for someone, or someone can enhance it, there also soft of unknow variables. As im not detaily user of these ancient stuff and had not good memory, i dont remember everything from top of my head. https://www.vogons.org/viewtopic.php?t=61823 I will report more incompatible Programs if will find them here: - ThightVNC server 1.3.10 - Generate boot bluescreen (there not any driver or service names, just some generic memory values/adbress numbers mess), so far it did not tried to other VNC server, or move net start command in the autoexec, its started at the start.. but suspect that the end of autoexec its still before VNC server driver /service is started, so it will not help..

Its sound nice in the highlevel, so can you make some shortened guide how to do it exactly?

I read utility description there is nothing about that is mainly for MS-DOS, in comparison Windows usage is mention 20 times and there is even mentioned in the most cases not modifications to DOS in most cases. In case of other his tools there they are like 80% for Win9x and if they are for DOS, like TRIM, it's usually stated at the top of the description. It has even own *.vxd file which is Windows only, if it would be for DOS, it makes not sense had it. Other reason is that creation of ramdisk for DOS, if my memory serves not needed any special utility just 1 line of code in Autoexec.. maybe default one cant be too big (i found some info about max 32 MB for DOS7 ramdrive). Why i have tried it? Well its for free now and Rloews tools in the overall are highly appreciated. Disk speed tests on the Windows 9x not fully reliable, but i have tried Crystal Disk mark for Win9x and it shows: 2 GB/s for Ramdisk, what is typical for Disk in the MS-DOS compatibility mode, for physical disks it usually means like - 2 MB/s and no DMA, what it mean for Ramdisk i dont know, but 2.2 GB/s on 2x Xeon 5160 seems nice - if not wrong Ramdrive speed depends on CPU speed too. Whitch freeware Ramdisk for Windows 98 do you recommend?

Hurah, i won, thx for help. I used Rayers method its restart Fest, but its working. Some notes: - its really strange way - used NDIS2 driver for Netxtreme II and everytime pointed install to it - its adding nothing into Config.sys - it is some driver loaded here its mess with other settings, so all its from Windows conf files or registry - at the start of autoexec is added around step 5 - C:\Windows\net start // So no binding - in restart after step 5, system already added net start, i had to disable it, otherwise system so freezing - you have to select no classic vendor like Realtek, Broadcom etc.. from list of Network adapter's by OEM vendor and name of the card - skipping means skipping network card detection after Windows logon - after step 7 i had to enable C:\Windows\NET start line - at step 8 - got classic Windows network logon screen and ping its working, all files seems to be loaded from Windows directory, so you can ignore C:\Net even you loaded drivers files from it. In device manager is Network card as any other normal one, its using C:\Windows\System\Ndis.vxd, driver date has date of installation Network panel also looks normally Network card neme, Windows network client and TCP/IP You have to now how to do it, because ist overcomplicated and not intuitive way, if someone actually invented this Workflow he was mad, im quite sure that it would be possible to do it with 1 or 2 restarts... In future maybe someone can use Filemon,Regmon etc, to find out what magic is happening create some Installer. I will make partition backup before experimenting with File sharing with modern Windows etc.. Im not sure if its is supported or not. I worst case i will use FTP client for it. Proven drivers: https://www.dropbox.com/scl/fi/5iza1z3eqerpvgafljok1/BroadcomNetXetreme-NDIS2-Win98-Proven.zip?rlkey=brh0bf67be3lfd76ytp6laxsi&dl=1

Ok i have tried these, but it seems that no ODI or NDIS driver like my 5708.. im sure that i had still some errors in configuration, but b57 driver (not NDIS not ODI, seems to be not compatible) in config should find card at least as other driver which im using.. What is nice with this solution is once i add card driver through Device manager, Network manager has all components its not empty. When i tried to add it through network manager, i got info that this plug and play card is not in my machine.

I have a bit problem to make rloew Win98 ramdisk working, this could help someone else, its handy add pause commands at the start of autoexec and after ramdisk command to see what is happening too.. Config: REM HimemX from Freedos; Its giving 2 GB of Ram for Win9x; After using Ramdisk is Ramsize 2GB - RamdiskSize - for Ramdsk32.com DEVICE=C:\DRIVERS\HIMEMX.EXE /NUMHANDLES=64 /METHOD:FAST /VERBOSE REM Define memory space for ramdisk 40000 =256 MB ;80000 - 524 MB; V- is for verbose more info DEVICE=C:\WINDOWS\Himemex.sys /A:40000 /V REM you can use after Rloew memory patch also original HIMEM.SYS instead of Himemx.exe above, its giving me too 2 GB of RAM, REM I wind out that is more compatible at least with Paragon NTFS, i can NTFS partition on Ventoy NTFS USB drive Autoexec: REM RamDisk size in kilobytes; in 32 bit memory space - compatible with normal 16+32 bit programs RAMDSK32.com R: 256000 REM Ramdisk Label LABEL R: RAMDRIVE I have tried to set Himemex.sys before HimemX.exe, but it not worked, i was getting /E parameters errors, i think that parameters where right.. regardless you can use this as the start, manual its to be a bit low level. Its using PROTHOOK.VXD default method, which need to copy prothook.vxd in Windows\SYSTEM directory and add device=prothook.vxd to system.ini at the start of [386Enh] section. If you need to use different mode just add /S or /I as the first parameter before /A:xxxx /V So far i did not tried to use Ramdisk as Swap, but its described in the readme as option, you can also defined multiple smaller Ramdrive in the dedicated Ramdrive space defined in by this line DEVICE=C:\WINDOWS\Himemex.sys /A:40000 /V Only problem is when i open Control Panel->System, there is info in performance tab, that ramdrive letter is using MS-DOS compatibility mode file System.. Maybe its only visual thing, because its using FAT16 or something like that.

Thx, i have to use wayback machine to download it, for some reason. I made mod of this it was only slightly different DEV iD and added new F_NAME3 variable : PCI\VEN_14E4&DEV_164C&SUBSYS_01B31028&REV_12 ; im using only start of it and ne name defined bellow %F_NAME3%=k57.ndi, PCI\VEN_14E4&DEV_164C ; I hope that only start of string without SUB.SYS** its enough and defined new name at the end: F_NAME3 = "Broadcom NetExtreme II 5708 Gigabit Ethernet" Other interesting thing is that *.cat file line is disabled so seems to mandatory. Now im only confused, when i have to use this file, before i used oemsetup.inf. I will try to fiddle with it, i have now much more informations, but some details are still a bit fuzzy.. Here modified package with Broadcom 5708 added from the future preservation, just expanded by 1 more card - untested: https://www.dropbox.com/scl/fi/7z9oled5ah31wy8x19uqd/Broadcom-CustomMade.zip?rlkey=wumyr8jikte76od7iflxul2wi&dl=1

Hi, i managed to install Windows 98 on Dell PowerEdge 1950 - its intel Greencreek 5000 chipset converted to retro gaming ring, i have Win2000+ OSes already working. But i have problem to make SATA and PATA working with DMA, for some reason its not such slow as normal not DMA machine, im using Sata for System disk and PATA is for CD-ROM. I controllers is Device manager working - for these MS drivers or Rloew Sata / Pata drivers both works, i even tried PurgeHD utility from Rloew, which in for some reason todays Rloew tools collections (i added it into zip bellow with some older ATA driver and SCANHDC utility - i bought it back in the day), but there is problem with channels.. They have Exclamation marks. - there are Code 10 and Code 9. AHCIBIOS ulity does not found AHCI.. in bios is just ATA for sata port. I think that source of the problem is that, machine as very specific setup, just 1 Sata port and 1 pata channel.. and these probably supposed to work with multiple devices on one channel, or multiple channels etc.. Maybe someone know how to fix it. Controllers are from Intel -drivers are for Windows 2000+ Here are HWinfo, Astra and AIDA reports from Win98 on this machine + screenshots from all Device manager Storage controllers. I have tried to restore Windows 98 quick install image from the other machines on this HW too, there was the same problem with disk controller, but there seems to a bit more ATA / Sata drivers, there some drivers for switchable and fixed channels and whe i tried to point to driver, i got hudge list of possible drivers and wasnt sure which to use.. So far i not managed to export that more ATA/Sata drivers package form QuickInstall distro, maybe someone already did it.. I have tried multiple Windows 98 drivers packs, but nothing compatible was found. Its reported as: 1) Device Description Intel 631xESB/6321ESB - PATA Controller Device ID 8086-269E Subsystem ID 1028-01B3 2 ) Intel 631xESB/6321ESB - SATA Controller Device ID 8086-2680 Subsystem ID 1028-01B3 So far i found Intel 6300ESB Sata and 6300 PATA and later 631xESB/6321ESB drivers for Windows 98, but they seems to be just empty INF - device description change "drivers" behave the same ways and all others, at least its bootings.. https://www.dropbox.com/scl/fi/ao2md0edjyhnpyf0avx2t/Dell1950-HW-Reports-DiskControllers-Shared.zip?rlkey=fvkddtnrbfauv9iolb1homxu7&dl=1

I read posts above, but im really unsure how Dos driver is connected / reused in Windows 98. Its quite a long time when i used MS Net driver working in DOS, im usually using packet drive + mTCP is much simpler. Im trying to make Broadcom Netextreme II 5708 working in Windows 98. I made to work Broadcom Netextreme I - 5703 and Broadcom 5721 in the past, but i have not found working driver for 5708, i have found quite and lot supposed Windows 98 driver for it, but in driver is allways mentione W9x.cat file or there is used - b57w2k.cat from Win2k, which without is not included, i dunno if these drivers are just fake, or i dont understand something. I dont fully understand how Broadcom 5708 driver is working, because in more modern OSes have 2 parts - some system device with Broadcom 5708 name and 5708 Network card, maybe its some server remote control thing or its support device and both has to work together. Netextreme I does not behave like this. So i decided to try to make Dos driver working in Windows 98. I managed to get lan card detected by broadcom *.dos driver is able to run by these in autoexec, i had to use lsl.com, because without it i got error, that is not loaded.. C:\NET\LSL.com C:\NET\Bx2.com // LineSpeed is regocieted + C:\NET\net start In config is this: device=C:\NET\protman.dos /I:C:\NET device=C:\NET\Bxnd20x.dos but in Windows ping etc is not working: When i try to add netbind - as i saw in some tutorials, im getting error: C:\NET\net start netbind Error: 5745: The protocol manager could not find protman.exe, try to removing any currently installed protocols and adding them again. I copied protman.exe and other files from Windows 98 in C:\Net and its in the path. Where is a problem: - there is a lot possible variables to comment and uncomment in Net.cfg - same with protocol.ini So it needs someone who understand it more, or some good tutorial, because try one by one, seems like a lot of work and it not guarantee to make it working, its possible that more than 1 parameter is needed. When i tried to add NDIS driver through Control Panel->Network as is supposed above it seems that its only rem Network line in autoexec and config, i have Network card in the list of system devices, but Network panel is empty. Here are are my C:\Net files except those from MS, because of licencing, but i have these files copied into C:\NET https://www.dropbox.com/scl/fi/kqlad994wa6znelyqj30a/DellServer1950-Win9x-Net.zip?rlkey=49704e3h1h7t9j951azezot5v&dl=1 Best i have found is this info: https://www.tek-tips.com/threads/ndis2-driver.784895/ also found on Win98 CDROM \tools\reskit\setup.exe or the...\help\98Rkbook.chm [?] (2-3mb) more text from MS; "Overview of Network Adapters" Chapter15 Real-mode NDIS 2 support. An NDIS 2.x protocol under Windows 98 must use an NDIS 2.x network adapter driver. Both the protocol and network adapter drivers must load and bind in real mode before Windows 98 runs. Values in Protocol.ini are used to load the real-mode NDIS drivers, as described in Chapter 16, “Windows 98 on Microsoft Networks.” However, you still use the Network option in Control Panel to configure NDIS 2 adapters. When you run a real-mode network, Windows 98 uses NDIS 2 versions of NetBEUI and IPX/SPX protocols. These protocols are not intended for everyday use, since Windows 98 supplies faster protected-mode versions of these protocols. Windows 98 also supports existing ODI drivers with Novell NetWare – compatible network clients. For information, see Chapter 17, “Windows 98 on Third-Party Networks.” => 1) DOS driver to be loaded in DOS. 2) Protocol.ini is used, but nothing about its parameters details. 3) Its needed to add Network control panel device.. But im not sure that for Particular part, or just use generic Existing NDIS2 driver option. 4) Im not sure if NeBEUI and IPX/SPX are just optimal, or not, there is nothing about TCP/IP. Does that part about them means, that if get TCP/IP working that i can add classic not real Dos mode IPX and NETBEUI versions? 5) Bind is needed to make it working - my problem. 6) Not info about NET.CFG, maybe / probably its only for the part which i already make it working. It would be handy if someone who made it working can just upload working settings, change for other cards, should not be too hard. I have found some tutorial from Rayer for Win9X too, but there is not netbind and some parts like skip network are not clear, it means probably to setup start step by step and not run some part of configuration, but it be tricky and leads in blue screens, especially if you dont have Windows 98 CD ready when Windows are trying to setup network: https://www.bttr-software.de/forum/board_entry.php?id=22118 Its translated by DeepL so it could contain errors: 1) Control Panel|Network|Configuration - remove the old adapter "Realtek RTL8168/8111 PCIE-E Gigabit Ethernet NIC" 2) in Device Manager, remove existing network adapters 3) Control Panel|Network|Configuration - Add|Adapter|Add|Existing NDIS2 driver|From floppy disk and point the path to OEMSETUP.INF and let it copy the necessary files from the Windows installer (PROTMAN.DOS is needed), reboot 4) after reboot, skip the network detection 5) a new disabled network adapter "RTL8168/8111 Family Gigabit Ethernet Adapter" will appear in Device Manager Enable the device, on the Driver tab click on Update Driver|Next|Show list of all drivers|Existing NDIS2 driver|From floppy disk and show the path to OEMSETUP.INF, let it install "RTL8168/8111 Family Gigabit Ethernet Adapter" from %TEMP%\~oem095B.WIN point the path to RTGND.DOS and let it copy the necessary files from the Windows installer, reboot 5) after reboot, skip the network adapter detection 6) in Device Manager, remove the "RTL8168/8111 Family Gigabit Ethernet Adapter" network adapter, reboot 6) in Device Manager, remove the "RTL8168/8111 Family Gigabit Ethernet Adapter", reboot 7) after reboot, when the network adapter is detected, select the driver from the list|Network Adapters|Show All Devices select the manufacturer "oem" and "RTL8168/8111 Family Gigabit Ethernet Adapter", let it install from WINDOWS\INF\OTHER\~OEM095B.WIN and copy the necessary files from the Windows installer, reboot 8) After successful installation, the PROTMAN.DOS and RTGND.DOS files should be in the WINDOWS directory, in AUTOEXEC.BAT line C:\WINDOWS\net start, in Device Manager, one entry Network Adapters|RTL8168/8111 Family Gigabit Ethernet Adapter with the NDIS.VXD driver and the Resources tab, and in Control Panel|Network|Configuration also 1 item "RTL8168/8111 Family Gigabit Ethernet Adapter" (NDIS driver for real mode) Here is original source, you can use own translator: http://www.rayer.g6.cz/hardware/gap67ds3/ndisinst.txt Its linked from here - there is some intro: http://www.rayer.g6.cz/hardware/gap67ds3.htm#WIN98_NET and http://www.rayer.g6.cz/os/os.htm

Well, i used file form link above - its named oem.inf made it matters, i expected that there is some default file, but there is not, you have to generated through batch.exe setup located on Win98SE cd in \tools\reskit\batch\ (optimal.ini file seems to be needed to run it) - yes you can save it empty / default, without really using the setup. I have tried to fill all the data in setup wizard, it still working fine on Windows 10, but there are not data which you posted above, question where exactly put these, it script, but its sequential so location matters. I have found: [Install] section, with contains this values: AddReg=RunOnce.BatchDelay,Run.Installed.Components,Skip.PCMCIA.Wizard,User.Profiles.Reg,User.Box.One,User.Box.Two,Registry.WinUpdate its between [Printer] and [RunOnce.BatchDelay] Its the right section where to put these files, or it more [Install] section are possible and i have to put it elsewhere? My new file, where through wizard is attached, its very similar to file which i used form the link above. BTW its normal, that autoexec.bat and config.sys contains only setver in autoexec.bat and they are completely empty? Im not sure, but i had some system attrib tags on old files, so maybe they could not be removed by the setup, or if they already exists, setup is not modify them.. I have bad memory so i dont really remember, i was used in not english install there where always somethin to set code pages etc. Win.com switches - it would be great, if you understand them, to add some description there.. I dont understand is for example this - "EMMExclude=A000-FFFF" is still related to Windows not MS-DOS fallback or MS-DOS mode run from Windows Desktop.. Usher's-method sounds interesting too. Well i had to already edit settings - i mean manually add /Numhandles=64 (BTW what is better 64 or 128 for me there are just magic values) parameter, its nice to know that this exist for machine, where is not himemX.exe yet copied. Otherwise in not big difference add HimemX edits or Himem.sys switch parameters. Unless its possible add Himem.sys parameter right into install script. Other option how to bypass is run Rloew patchmem /m ; or even intergrated Rloew Mem patch right into install *.iso, so far not looked in how to do it. Otherwise i was able to reach normal mode, after Rloew patches install by running: patchmem // i forgot /m parameter maybe it matters // but with io.sys and himemX.exe and vcache is probably not needed anyway ptchsata - and copy Sata.inf into Windows\INF folder, INF folder is hidden - it may to be visible by Filemanager in default settings. Front USB are working with default USB and nUSB drivers, card machine USBs, whare are using different USB 2.0 controllers, not working yet with default or nUSB drivers - i have tried 3.5 there are supposed to be "better".. and all other drivers hell.. msbatch-RuThaNgeneratedBeforeManualModification.zip

Ok i finished installation, with attached script + batch file to start it, just change your Windows 98 product key, you can edit other things like hostname or Windows folder name etc, but like 99% of these except product key could be edited later. I was not entirely smooth, after second its there was freeze on HW detection, problem could be loaded USBDDos.Exe /Hid driver, i loaded it by mistake. It also seems that script is not deleting (or because of some bug at least not my machine) Autoexec.bat or Config.sys - stayed and in config was already HimemX.exe line to fix 512+ MB problem. DEVICE=C:\DRIVERS\HIMEMX.EXE /MAX=1148576 /NUMHANDLES=64 /METHOD:FAST /VERBOSE Normally is in this phase, my machine crash with io.sys and himem.sys error and i have to install io.sys 512+ MB patch and copy himemX.exe instead Himem.SYS to Windows directory... and had line above in config.sys and change vcache parameters in WIndows\System.ini for these: MaxFileCache=261120 MinFileCache=32768 ChunkSize=4096 I already replaced WIN98_54.CAB with Rloew patch, but other patches are probably needed to bypass manual io.sys patching. After one more restart, i installation finished, i saw how it progress fine after Computer name screen, all seemed ok, and i got stuck on shutdown screen, machine not should down (which i my machine specific), so i restarted and next boot freeze, which i sort of expected.. I tried to boot in safe mode, but got IO.SYS crash as expected - so i patched it as above and copied again himem.exe into win directory (before i loaded it from other directory) and edited system.ini - after it, i was finally boot into safe mode and i desktop loaded = installation finished.. if not you will get info, that installation not finished and safe mode is not available.. So all fine, i now will make partition image.. and fiddle with right RLoew driver get SATA controller in ATA mode working with DMA, which is probably reason of non safe mode working. Its Dell PowerEdge 1950 modded for retro gaming so i not expected easy job.. its using wild storage IRQ like 23 and 78. At the end make own unattended script mod wasn't hard and it does not took too much time. Thx for help. After i plan to mess with NT4, which seems to be even more "fun", so far its rebooting during setup loading... !Unattended-AutomaticInstall-ToQuickInstall-AndBy-No-Working-KeyboardAndMouse.zip

Ok i have created whole new script, with all parameters, now its running, im will let you know and upload the script, in link above are parameters without description i found and added a bit more explanations to the script. I run it this way: setup RUnatend.INF /ie /im /is /iv /nr ; name of batch has to be before parameters, also it took quite a lot of time to start, after initial progress bar reach 100% There was only problem with warning messages about first NTFS partition, its SU0012 abd SU0015.. Im lucky enough to have mouse and keyboard running at the start of install, but someone could not have such options. Im not sure if it could be fooled, but hiding this partition and of course, you can make backup,delete it and recover it after Win98 install.. Or maybe its enough to make FAT32 partition first.. I made NTFS partition first, because Windows NT bootloader at least on some machines has i problem to start far from disk start, im not sure if problem is 2GB or 8GB and it could change if service pack integration to WinNT installer. Other i copied win98 directory on the started partition and and started it. Other issue is that setup has to be started from FAT32 primary active partition on the first disk, otherwise it need FAT32 or maybe FAT16 on the first disk.. So i removed SCSI controller with Disc Array which was reported as first disk. I btw found some project using BootIT manager and FAT16+ partition hiding for all systems from Dos+Win3, to Windows 2003, all except Win NT4 which maybe really require NTFS or FAT32(less likely).

Well question is i can use it in the middle already started installation, or i need to start whole installation again? I have found some unattended script here, it seems that it could be possible to replicate the steps manually.. Im only not know if every small step would be saved by installation progress or not.. because it would make it much more complicated. I also struggle to find some GUI regedit compatible with Windows 98 to use it from Live Windows CD, registry they have different structure and and the most of Registry editors are for NT4 or Win2000+. I tired to find some GUI WIndows registry editor for Linux, but it does seems to exist, there is only CMD line one chntpw use like this: sudo chntpw -e /media/mint/WinNT4-System/WINNT/system32/config/system // You need different patch based where you Windows install is located and how that partition is mounted inside Linux and its annoyingly CaseSenSitiVe It works fine for WIndows NT, but not for Win9x, not recognize is structure when i point it into system.dat , or user.dat There are Registry reditors, which are running fine on the live Windows 9x settion like Registry Workshop 2.x, but load registry hive from the other partition seems to be problem. Windows XP inbuild registry editor is not compatible with Win9x hive, or im doing something wrong.

Hi, im trying to install Windows 98 on machine without PS/2 ports, only with serial mouse working, im stuck on computer name screen, where is empty computer name and i have to put some name in it. There is not any USB legacy setting in the bios. I have tried Windows 98 quick install, but disk controller is not found, but stock install is see disk fine. I already reported Quick install bug. https://github.com/oerg866/win98-quickinstall bug - https://github.com/oerg866/win98-quickinstall/issues/41#issuecomment-2912779878 I also now there is unattended install options, but im afraid that it will mess with disk partitioning. Have USB keyboard working in DOS - have tried USBDDOS driver: https://github.com/crazii/USBDDOS , but its not working for second part of the install, only mouse does. So question is can somehow edit some install setup files or half installed registry add insert needed strings like Computer name and later Windows serial Key. Maybe i can just one only part of unattended install script.. Tried to google this problem, im not first one with it, but i had to found right keywords..

Hello, i have tried to research booting from vhd, it could be practical, but so far my results are not great. I expected to find much more articles about it. 1) Windows 7+ BCD - its its working, but its limited It seem to be limited to Windows 7 or maybe Vista. Later Windows 10/11 are probably able to boot Windows 7+ machines, but its not possible to boot Linux from vhd. Problem is also how to create VHD for it: a) Because tutorial are quite long im not sure if possible to install Windows from live Windows session to some VHD. b) People are used to create VHD through some virtualization software, but there is after problem that physical HW is different that real hardware. I managed to connect virtual disc in Windows and use Paragon HW P2P adjust to add real storage drivers to make it bootable, but its commercial products and it seems that from more modern versions P2P adjust from live Windows sessions for other partitions where removed. There is some old 2010 version with P2P adjust for the live Windows session.. Because connecting VHD from WINPE or Linux based boot disk, not working or its complicated. Yeah can install Windows on physical partitions convert it to vhd image and delete original partition, but it needs possiblity of live install or some enhanced OS installer which is able to connect VHD as installer target partition - im not sure if it exist, again Paragon has some OS migration tools and there are some OS migration tools from other companies too - some proven tips for them would be great. Ventoy USB loader, has optimal Windows 7 / 10 /11 plugin too, but egain you have to adjust VHD for real HW boot. Hyper-V machine probably can be booted from Windows 10/11 bootloader. 2) Plop VHD loader its from 2010 - https://www.plop.at/en/vhdloader.html not more updates, it needs FAT32 partition on the same disk from its executed (it cant find vhd on other disks - i have tried it).. im able to run it from Grub2Dos, but i have tried to run NT4 vhd - vhd file is found, but not even reached Windows logo, i will try other OS images later, im not sure if this not dead end. Fat 32 mean that is limited only to max - 4 GB virtual disk, fixed and dynamic disk image sizes are support, but im not sure what will happen when dynamic disk size would try to get bigger than 4GB.. Vmware can split vhd into multiple fixes, but i doubt that is supported by this bootloader. Update: i 1 tested like 10 Pcem (86box) vhds with old oses, but even OS inside virtual disk has to be FAT32.. I often get classic erros like invalid disk or missing operating systems, i only managed to get Win3.11+MS-DOS 6 vhd to get futher than booting message.. i get MS-DOS started, after some config execution error.. so no config commands processed, afte that i got into command line, dir / cd worked, but otherwise wrong data i subdirectories and execution tools like edit failed, win.com failed too.. for some valid command i got invalid command. I have to check it, but it seems that these vhds where FAT16 not FAT32. It seems that very specific vhd disk format version is supported, in project description are not details, only info that dynamic size is suppoted too. Maybe *.vhds are too new for 2010 tool. Im not even sure if there is vhd format downgrade too (i prefer GUI based one). My vhds, where no stored at Win98 FAT 15GB partition, second after 15 NTFS - NT4 partition, on 500 GB Sata disk (in ATA mode in Dell server Bios, i guess that means IDE PATA mode, because disk is visible by Windows 98 CD-Rom command line and Window 98 start up floppy disk. 3) Grub 1 (Grub4dost) / Grub 2 So far im failing to find good tutorial for Grub 1 / Grub 2 vhd booting, i found some supposed success stories, but they often lack some important details. 4) Yeah i know that are bare metal virtualizer as ESX, Unraid, which are using virtual disks, but its something else, that add some vhd boot to existing machine setup - yeah i know i could simply create some Unraid physical disk and use special BIOS / EFI entry to it and kept existing normal booting machine untouched, its not quick or easy to setup how configuration.

Unfiltered log has like 50k of lines, if you are willing to check it, i will upload it. I have tried to check output of these processes, but it seemed like generic installer checks, i did not see anything suspicious in the log.

Thanks. It seems that is locked behind some classic big companies machine support / maintenance fee Paywall not just some MSDN MS partnership or OS licence. IBM / DELL / HP were big enough to sell it, maybe others. Yeah this text is clear: Windows 2000 Datacenter Server — update to SP4 only in conjunction with your OEM Some per vendor mumbo jumbo is needed probably like 1 more key in registry as is typical in these situations. There is dedicated MS Windows 2000 data center page: http://microsoft.com/windows2000/datacenter/default.asp I have tried procmon, first time i got bluescreen, but later i have find its old versions (1.0.0. to 3.0.3 worked) here: https://web.archive.org/web/20071011001855/http://www.microsoft.com/technet/sysinternals/utilities/processmonitor.mspx a they worked, but maybe bluescreen was not related to its version. I at least learned how to better work with its output. filter it.. i expected that it would more clear and it would collect only data per selected per process, but it seems that by default its collecting everything like Filemon and Regmon and its merged together. Here is filter report, i did not find exact call.. by my money are not something in these 2 keys, where are details about OS type: HKLM\System\CurrentControlSet\Control\ProductOptions HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion Here is filtered procmon log, its from install execution start to click to confirmation error message, i filtered it down to like 150 lines: https://www.dropbox.com/scl/fi/ug6frpi7lqcqpfhbh2ll2/SP4-InstallProcMonLog.PML?rlkey=i18n1xdbb0troxqgdooxf2l2t&dl=0 Its interesting that i can install other OS updates fine, just not service packs. It seems that only main advantage of Data Center is more RAM and cpus (i dunno how cores and SMP count for Win 2000..), with PAE (just through adding /pae to boot.ini was needed no hal fiddling) i have 10 GB of RAM.. 2nd highest edition Advanced server should be limited to 8 GB, Datacenter to 32GB or 64 GB, 32GB is mentioned online, 64 GB in IBM manual linked above.. maybe its 64 GB for the whole cluster, im not sure, how it works. In these days, would only make sense to solve this, because some retro computing preservation, to preserve highest possible version. As i wrote install SP4 right away is working, but someone could be interested to check original SP1 version and test and check newer SP, one by one.. and that is not possible.. doubt that someone will still pay some maintenance fee for 20-15 years old machines.. its not just support per platinum Dell account globally.. Other use case when someone could hit this problem is very old server migration to virtual machine. In case of Windows 2000 i found out that there is a lot programs requiring SP4 to work, i mean much more than SP2 / SP3 for Windows XP or SP1 for WIndows 7. Workaround is upgrade server before migration, i guess that nobody would run updated server anyway.. Its sort of like TPM check for Win11..

Yeah i should give it a bit more of effort and make screenshot, i hoped that is known problem I meanwhile i have tried to install clean with custom CD image of Datacenter SP4 from Archive.org it worked fine with original system key.. Luckily when i run SP4 again message is still there, this is exact text: The Service pack 4 (2,3 etc..) not been qualified by your hardware vendor for installation on this copy of Windows 2000 Datacenter Server. Please contact your hardware vendor for additional information on obtaining a Service pack 4 that has been qualified for your system configuration. But i would still like to know there was a problem and if its possible install SP4 somehow, or upgrade / downgrade Windows 2000 version or install SP from live system. Its possible for XP+ I researched a bit more research and it seems that datacenter really was somehow special, because Windows legacy update and update restored both report Datacenter as unsupported.. with note with a link to manually download updates, there is internet wayback machine link to Microsoft page, where i can download sometime, problem is that exact download files aren't archived I also do not understand how PAE is working with Windows 2000, Advanced server and Datacenter are supposed to support PAE. more than 3-4 GB of ram, im stuck at 3.5 GB.. its probably needed to fiddle with HAL files somehow. Because more CPUS and RAM support should be a main Datacenter advantage. Update: It seems that PAE needs to be still enabled manually by boot.ini edit: https://webhostinggeeks.com/howto/how-to-enable-pae-in-x86-32-bit-windows-server-2003-and-2000-to-use-more-than-4gb-ram/#:~:text=To enable PAE in Windows,The Boot. I checked Dell CDs too, there is indeed OS install assist, problem is that it support only raid drives during OS install process are all data on raid deleted.. so i dont not tried it now, maybe later i will try with another empty disk. There are also some Windows 2000 SP4 Dell flavor OEM cds on archive.org, so maybe you needed one of these.. still would be nice to be able to bypass vendor check, i have tried Regmon and Filemon to detect what is checked, but i never get enough skill to be able to filter their output to debug these things..

I got some old company Dell 1950 server for experiments, it came with Windows 2000 Datacenter SP1 installed. As far as i understand Datacenter is some uber special version of Win 2000, it was released with SP1. I have tried to install SP2 / SP3 / SP4, but it always fails, if get message its some about unsupported version. When i run Datacenter cd with newer service pack im getting message: that this vendor HW is not supported. Is there way how to bypass it this check? I tried to google it, but not found anything usable. I never was big friend of server vendor zillion cds images joggling and their OS install assists, but maybe you have to use some utility like it for this. I would understand if i would have same problem with random virtual machine or generic PC, there should be some Dell service tag in the bios and SP1 reinstall run fine from bundled cd, i tried generic version from archive org and its the same, so its not key etc problem. BTW its possible downgrade Windows 2000 server version without reinstall?

Its 16 years i know, i found the last update from 2016, and release from 2011: https://www.tapatalk.com/groups/win2kgaming/oldcigarettes-windows-2000-xp-api-wrapper-pack-ocw-t7.html There is mentioned v11, on BlackWingCat side is v10. I was always searched for universal tool to fake selected programs to thing that are running on different Windows version, so far it did not found it, it should be much simpler than adding missing kernel functions etc.. I found only some registry hacks to fool whole OS version, which is quite dangerous. Dos had some faking old MS-DOS version number inbuild too, in like MS-DOS 6+ or so. I would love to fake Windows NT4 to Windows98, because there are lots of programs/games which just refuse to install on NT.. but if you install them on Windows 9x and copy files to Windows NT machine, they are actually running fine. Other solutions of similar problems is just editing to *.msi installers through tool like - https://www.masterpackager.com, to lower required msi installer version or other artificial requirements which could prove as unnecessary.