ruthan

Ok, i have tried another approach meanwhile, there some guide how to install Windows 2000 on Intel Sandy Bridge and later: I have managed to install Windows 2000 with standard PC mode - without ACPI meanwhile by switching bios to ATA mode and press F5 and integrating UniATA driver. I have tried to create CD by this tutorial, but its still stuck on Windows 2000 setup loading, unless i press F5/F7 and select Standard pc mode, but tutorials has 12 steps (it would be really nice to make utility to make it more effortless ), to i could do something wrong.. I used BlackWingCat AHCI drivers too . There is also known problem with usbhub20.sys, which has to be manually delete to setup to progress, i did not found solution for it (i mean from install cd fix point of view). Im not sure about point 12, its still needed to replace acpi.sys even when patched version it is integrated on install cd, or its mean as upgraded for already installed machine in not acpi mode.. In case of XP, changing from not ACPI to ACPI usually meant to mess with different hal.dll and kernel.dll files. Question is if i can install Windows 2000 in ATA mode, install AHCI driver in advance, switch bios to AHCI mode and be able to boot in AHCI mode after. I selected different version of Windows 2000 than original one, so i have now 2 versions able to boot on the same partitions and i can play with both installation. I wanted to test, if installation would be repair by reinstallings, its not.. not in case, when original install is using Windows folder and new one WinNT, it seem to be hardcoded in nlite mods. What is good machine is now booting in ATA mode, to Windows 2000 bootloader, but i can fix it later..

Ok, i will check it, but i guess that simply copy some file on system32 folder would not be enough, it probably needs also some registry or system file change. What is really strange is that Paragon - 3 different versions (so its not just 1 version bug), considering Microsoft VHD controller driver as boot critical for this installation Windows 2000.. even its probably does not exist.. vhdm* i searched whole Windows 2000 registry / partition / archive inside for vhdmp* string, but got nothing.. If my memory serves its not first time when im using Paragon for Windows 2000, so it would be strange if its using Microsoft VHD controller to make machine bootable.. or its some Virtualbox, Vmware, Hyper-V migration left over.. txtsetup.sif , i never saw such file, im used to using txtsetup.oem I also tried to reinstall Windows 2000 from cd with keeping data, but even when Disc controller hw was loaded from USB floppy.. it froze on Windows 2000 setup loading.. I have found that is probably because some ACPI incompatibility - and you shrould press F5 / F7 to disable it.. So far, if pressed these keys im got into some menu, when i could select machine type, but there was no any ACPI settings, but just Standard pc / Standard 486 and some OEM machines, this way i got through loading freeze, but it ended with Inaccessible boot device blue screen right after. When i tried to load Fernando 2000/PX AHCI drivers : https://winraid.level1techs.com/t/guide-integration-of-intels-ahci-raid-drivers-into-a-winxp-w2k3-w2k-cd/25310?page=1 from floppy, i could select driver on USB floppy it was found, but later i got file is corrupt error / multiple times - USB floppy could be a problem. So i have tried newest nlite for Xp and slipstream AHCI drivers - Fernando ones or Universal Ata driver- https://alter.org.ua/en/soft/win/uni_ata/uni_ata.php (if im not wrong there is not some OS install floppy version, so i have created something with *.oem file ), but so far im getting for both drivers if my memory servers, some inf line 53 parsing error. I will try some other Win2000 nlite image and double check if i removed Fernando drivers, before i added Universal Sata.. and use only need 1 Fernando intel AHCI device driver, not all Intel controllers.. There is also some certificate as part of Fernando drivers, im not used to drivers certificated for 2000 / XP, so its really needed, or has to be injected before driver is loaded, to make it working.. I hope that i will find some working combination of settings to be available to start Windows 2000 install refresh. I have using real CD, in Sata drive, no USB flash disk install - there is not Pata. Yeas, i can try old more refresh Windows 2000 image from backup or remove virtualbox / inject AHCI drivers before creating virtual image for migration.. There is also WinNTsetup utility - https://www.majorgeeks.com/files/details/winntsetup.html which claims to support Win 2000 too, so i can try to check, if only for clean installations or it could make refresh / reinstall. So i not out of options and maybe, maybe i will even learn something in the process.. There are i quite a lot of unknown variables.

Thx, Ok i found it, problem is there are 2 menus, first dos, where is registry tools option too and second on the Live CD (right one). I have tried 15.2 DVD, but Live Win7 refused to boot for both method, for some reason its trying to read something from the MBR.. and reporting no MBR magic fail error. 15.2 CD version with Live XP worked fine. I was a bit afraid how targeting would work, but you simply from XP, select target temporary path. Luckily i found this tool standalone too on Github too: https://gitlab.com/wiert.me/public/windows/xp-2003/fix_hdc.cmd/-/tree/main?ref_type=heads Im only unsure from which OSes it could be run, if it needs to be executed from WIndows XP / 7, or its possible to run from older / newer versions too. It fixed XP boot for me, even in AHCI mode - i not sure its influenced that i already had AHCI drivers added before through Paragon. I did the same thing, include AHCI driver - Its intel c216 controller for Windows 2000, but this is not working, im still getting INCCESSIBLE_BOOT_DEVICE error in middle of loading bluescreen- classic - 0x000*7B (0xF5C1B84C,0xF5C1B84C,0xC0000034) error. I repeated it twice, tried to add before or after AHCI drivers inject. Im not sure maybe it needs to boot in ATA mode, but now when i have 3 of 4 OSes running in AHCI mode, change all to ATA because of 1 of 4 is not prefered option. Im not sure, its not because for some reason its than VHD driver trying to load.. I found some strange thing - there was of this driver mentioned in autoexec file, in with REM.. why i dont know autoexec should be skipped for these old anyway and i dont have DOS or Win9x installed.

Where exactly and in which version of Hirens is this tool, did not found it Dos menus its on the live cd?

Thanks for info, interesting thing is not found vhdmp.sys for this dummy / virtual disk in virtualbox machine, before migration. Its called Microsoft Virtual.., but it seems that such driver get from the Microsoft but i did not found it on Windows ISO or on Virtualbox Additioon CD ISO, i searched within archives too, but it still could be embedded within some *.exe installer, in some update, but not even found on *.vhd. Its mystery Hyper-V - i found some tutorial for it, but it did not helped for my machine. Please claiming that its working for some physical machines too, its some minimal default set of Registry keys to make machine to boot: https://learn.microsoft.com/en-us/archive/blogs/michs/p2v-migration-issues-with-hyper-v-stop-0x0000007b#required-registry-critical-boot-entries Other mystery is still why Windows 7 bootloader is not started after switch from ATA to AHCI, im not sure, there are some variants of it, except EFI / MBR version, or there is some additional configuration / drivers settings possible.. Thanks for tip about Hirens Boot cd, did not know about such tool on it, i will check it.

I have also tried boot other boot loaders like Plop 5 or Paragon WIndows OS detection fallback from its live cds, but it seem that they really dislike Dell CSM->ATA mode and with combination of this partition scheme. 1) Boot partition - FA32 with Windows 7 BCD; primary active 2) Windows 2000 - NTFS; primary 3) Windows XP - NFTS; primary 4) Extended volume: 4a) Windows Vista 32 4b) Windows 7 32bit 4c) NTFS - Data partition I was inspired by quad boot project - with Windows 2000 / XP/ Windows Vista / Windows 7 project floating around on archive.org etc, i created my own Virtualbox vhd with same settings, before i was not using separate boot partitions, but used standalone install per partition loaded through - Grub2 on Linux partition (there is not problem with extended partition - as far you have to force grub2 install through some warning and boot repair live cd, does not like sometimes).. or Grub2Dos.. or Plop5. Everytime when i feel that i understander booting and bootloaders, i met some new situation, when something is not working as supposed too.. Im getting better, but still i can spend days to make something working, or have to use multiple bootloader and use specific boot managers chainload to boot specific OS as i want, for example Grub seems to skip for some use boot.ini where is PAE switch and im unable to force /pae other way that through boot.ini - if someone know solution for it for 2000 let me know..

I have Dell Optiflex in CSM mode - MBR disk, whith the same error.. Im migrating Virtualbox machine, problem is there i WIn7 bootloader which refuse to start after AHCI to ATA Bios change and in AHCI mode, WIndows 2000 and XP, ending with this error. Windows 7 and Vista are booting fine in AHCI mode. To make it more complicated when im trying to use P2P dissimilar HW adjust tools from Paragon, its asking for Microsoft VHD Loopback Controller 32bit and im unable to find it for Win XP / Win2000. I searched Windows XP registry but i dont see there request for this driver, maybe its some virtualbox drivers left over. I have found - vhdmp.inf as part of lots of XP drivers, its requesting, ServiceBinary=%12%\vhdmp.sys and vhdmp.sys,,,0x100 ;COPYFLG_PROTECTED_WINDOWS_DRIVER_FILE , but so far i have found vhdmp.sys only for Windows 64 bit or Vista+ 32 bit. I searched Windows *.iso disks for it but found nothing, also on Win 2000 / XP booted partition already. I suspect that problem count be too, that Windows 7 is starting from the extended volume.. the is small first active partition with Windows 7 bootloader, but maybe in ATA mode it is not able to boot from extended partition as in case of AHCI mode, its strange.

Well, is there some test, can test performance without and which vcache used? If yes we can test with its size make a difference impact, if it has even some reasonable effect.

Hello, does some know some proven utility for NT4? There is in build Disk utility, but for some reason it reports even some not system drivers as locked, there is not even swap on them so i dont understand how to unlock them. There is option to change letter after reboot, but its not working at least in some cases (on my system it worked, sometimes i needed a few trie, but now it stopped to work for some reason.. - im not sure if preboot partition mapping tools are actually executed.. - maybe bootmanager (Grub4Dos->Plop->EasyBCD) make difference and some sequence is skipped.. ) - letters are still the same after reboot, when i remove letter not assign them, after reboot are still drive letters mapped. I have tried Acronis partition tools, again they require reboot and nothing is changed, my guess is they simply count on Windows 2000+ solution. I have tried some old Paragon tools which i own, but it seems the same.. On more modern version there is something like force disk disconnection and force drive letter change without reboot, but in case of old tools still compatible with NT4 this is missing. More modern Windows are using these registry path for it: HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices Its not available in Windows NT4. I have found, something there: HKEY_LOCAL_MACHINE\SYSTEM\DISK - there some Information key, which are probably related to some partitions, but there is not some letter to which they are mapped.. Maybe its some binary / hex part of this value.. Other problem is there are just 2 values, i have like 7 partitions, just order these Informantion keys are used to map it for first entry to first free drive letter, second to second etc.. These keys are 920 character in size - its byte. Samples attached. I found driver letter character inside, so i have tried little switcheroo by replacing letters for intended, D for Z etc, but did not worked, good news its machine is still booting... What is interesting changes are lost.. So it looks like these values are somehow generated during the boot, or simply click on ok, after letter change in the right column is not enough.. I have tried to change both Info* keys. Maybe its possible to some trick like force cd driver letter to free some drive letter and use remove it and assign it after.. Or maybe disable physical disk device, if its not primary boot device. For Windows 98 there is drive letter assigner, but so far i did not found something for Windows NT4. I doubt that some boot cd could to do the same, because it would imply that NT4 hive would be loaded to write there changes. Because one disk is SCSI array i cant simply disable it - on bios level to make changes step by step.. Or not easily SCSI array settings are pretty limited and i can maybe do it, through special RAID manager boot cd menu.. Still, i would prefer some working Windows utility to do it.. I looked for some key in the registry, but i have found only keys for optical drives. NT4DiskKeys.7z

There was other method, patch for io.sys to support more than 512 MB, look here and use some Translate plugin: https://rayer.g6.cz/os/os.htm ; its in the block containing these: [vcache] MaxFileCache=261120 MinFileCache=32768 ChunkSize=4096 Rloew has partition patch IO.sys to support bigger disk too, maybe it also include mem patch.. Or its mem patching is patching other files, which are actually avoiding safe mode to crash by some other way. Method above was in age of max 1124 MB ram for Win9x, Rloew made even 2 GB working, or maybe even.. im not sure, i maybe saw 2.75 GB free ram.. and of course he has ramdisk to use the rest of ram, there are other Ramdisk to do some too.

1) Its simple unattended install file is using its own syntax, different that System.ini or System.cb.. its has hints where to place these values.) If you want make these changes later / manually after install is finished and edit System.ini and System.cb . You can copy these value to them - but they have their own sections hinted in the unattended strings.., so you cant just copy them at the end of the file as they are, but have to place them to section hinted + remove the start of string for unattended file, remove "" and end of the string.. and adjust to be compatible with System.ini and System.cb format.. Unattended file syntax: %10%\system.ini,386Enh,,"MinSPs=8" ; vs [WindowsDir]\System.ini syntax: // find [386Enh] section place there this value: MinSPs=8 It make sense to limit Ram size to 512 MB as in you unattended script values above, to finish installation which crashes, but later it make sense to install HimemX or Rloew memory patches to enable more than 512 MB. Im also not sure, if System support description after ";" at the same line as actual value, or it would end by parsing error and have to make comments on its own lines.. or not use space " " character in front of ; .. I got some blue screens, it could be some other typo / or wrong value.. or not compatible comment on the same line of contain space before ";" I mean: ; Comment MinSPs is very nice parameter MinSPs=8 vs MinSPs=8 ; Comment MinSPs is very nice parameter 2) There is most interesting thing vcache max size, above is this value: %10%\system.ini,vcache,,"MaxFileCache=56320" ; Q108079 If im not wrong its decimal - 56 MB, i had 256 MB and IO.sys patch also is hinting to use 256 MB if you have more than 512 MB ram. If understand bigger cache is better, as far as you not hit to max limit. If you have 2GB of RAM, sacrifice 256 MB for cache does not seems more. Im not entirely sure that this cache is for.. because more WIndows does not have such cache options and manage caches automatically regarding of info which task manager is printing. If seems that WIndows 7/10 are trying to use cache quite aggressively and free some of it if needed for some program - example i have now 19 GB of ram used - 17.7 GB cache and i Run just chrome - 6 GB ram and some resident programs like Email client, MS Antivirus, Dropbox, Afterburner etc.

Thanks, summary of this article if i understand it correctly is this: - if you uncheck PCI steering checkboxes in device manager, Bios resource settings is used without any adjustment on the Windows side - Checkboxes simply means tries to adjust device settings on Windows side (so it seems that enabled all checkboxes in the case - if you have some resource problem could solve them), order / priority of different tables is "hardcoded" you can change it - you can only disable some tables tries, priority is: 1) ACPI BIOS > 2) MS specification table 3) Protected Mode PCIBIOS 4)) Real Mode PCIBIOS // 3 -Protected mode is disabled by default - PCI standard supports more devices to use the same IRQ and it is different from the ISA, which afaik new unique IRQ per device Other i tried to find / read ACPI data - but best what i have found is in SIV utility - System - ACPI + Pnp (ACI Dev button is showing the same data)- but there is only a few device and at least on my machine is IRQ collumn empty and only useful column is really DMA channel info. Still unclear: If im not wrong, it make sense to fiddle with this settings only in case of IRQ problems, but it will not fix memory range ares problem? Unless changing IRQ could influence address range which is device using? DeepSeek AI - tells that in general IRQ and memory ranges are independent, but in other hand it claim that IRQ change does not force memory address change, but it may to do it.. - So response is something like, it may sometimes change memory area and help especially for ISA bus devices. Windows 98 does not change / adjusting ISA values at least by default. Why memory areas options are not available - it seems that in depends on the device design, if its design define 1 or more possible memory areas which device could use. Originally i though that there is some machine memory address pool, like IRQ pool (limited number of "free" IRQS) and that pool is full - in case that is not possible select different address area for the device.. - but its simply "laziness" of device developers which often does not offer alternative address ranges which could be used by the device and we as users cant override / change it..

Thx i tried all of these, system is still booting, so i hope that it would be more stable. Otherwise its is for unattended install, here 512 / 1024 MB limits have sense, to already installed system have sense to change/remove memory limits.. - Of couse, you have to remove "" + ; + the start of string (I.E - %10%\system.ini,386Enh,, ) - just to point you to right section of system.ini where you can place them, i placed the all for [386Enh] at the start of this section. I found description of most of them here: https://www.mdgx.com/lastweek.htm // Yeah links generated by this sites are strange Yeah that i was suggesting still you can forget and you should make some snapshot / backup (another catch) if you want to use Virtual machine after. Yeah i already looked into it, i would still prefer some GUI tool to do it, its faster and less error prone.. for example i dont remember right *.reg header from top of my head, so would have google it on other machine / phone.. or create file together. What seems strange i have tried to regedit with the same parameters on the live Windows 98 to make some automatic Erunt like registry backup *.bat, but it seems that all parameters, include /? are ignored.. so is not possible to use regedit in command line mode, or syntax is diferrent than it the Dos. We, i have still 2 major problems, others are details and i have tried everything what i was able. 1) Windows 98 - no working DMA on Pata and Sata controllers, because of exclamation marks on the Primary and Secondary channels components, controller itself has not errors. Server RAID Dell Perf 5/i also have only Windows 2000+ drivers. Windows 9x is only major older OS unsupported by nice Universal PATA /Sata driver - https://alter.org.ua/en/soft/win/uni_ata/ 2) Windows NT4 - not working driver for Network card - Broadcom NetXtreme II 5708, i dont have enough skills to modify oemsetup.inf for NetXtreme I cards, to at least to try a luck.. Windows NT4 inf for NetXtreme I card is quite huge and syntax is complicated - i tried, but im getting Card is not present error, because added Hardware ID is not working. I have tried Windows 2000 driver, but im getting Oemsetup is found in its direct and there is one, so its probably problem with dirent *.inf header / structure. Problem is that NT4 USB stack will probably not robust enough to use even USB Lan adapter. These details are in other my threads, so im almost there.. I learned this quite a lot of things, out of necessity, but its not enough

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. I found System.ini recommended parameters on this link: https://www.mdgx.com/lastweek.htm

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