oerg866

>Grab random hard disk for testing a few things in DOS >Don't pay attention for boot prompt >suddenly

I've already tried all of that (in fact, it was the first thing I tried). Thanks anyway.

GIGABYTE P85-D3 Should I list all BIOS options or what do you mean?

I tried two SCSI card with a seagate cheetah drive (LSI Megaraid 475 and DELL PERC-2/SC), same result, INACCESSIBLE_BOOT_DEVICE

Nobody?

Hi, i'm trying to install Windows NT 4.0 on a P85-D3 motherboard, and it's not working really. So far I got Windows 98 working without problems, but NT4 is being very stubborn. The issue is that I can't get it to either install or boot (assuming I've carried over the HDD from somewhere else), no matter what combination of IDE/SATA controllers and drivers I use. My previous board with the B75 chipset was working fine, but it had native PCI, but the 8 series chipsets ditched PCI and instead implement it via a ITE IT8892E PCIe to PCI bridge. I always get a BSOD saying "INACCESSIBLE_BOOT_DEVICE". Normally I know how to fix that, use a mass storage controller with NT4 drivers. But this just won't work at all. So far I've tried these things: Boot NT Setup via CD-ROM on onboard SATA ports, using UNIATA driversBoot NT Setup via CD-ROM on Promise Ultra133 TX2, using UNIATA and PROMISE's driversSetup via WINNT /B using Promise Ultra133 TX2 with Hard DiskSetup via WINNT /B using Promise SATA150 TX2+ with Hard DiskSetup via WINNT /B using onboard SATA portsBoot floppies via USB disk drive (doesn't work, I guess that's because NT4 has no USB support and access via BIOS interrupts stos when the kernel takes over)Using WinNT /B I have provided mass storage drivers using a USB floppy drive, when using the CD-ROM methods I have integrated the drivers (but i've also tried floppies using a vanilla CD). Last but not least I've tried running the first setup stage on another machine and then carrying over the HDD to the NT4 system, including doing a full install and running SP6, that didn't work either. So, I'm genuinely stuck for a change D: Any ideas? Cheers Eric

http://oerg866.titandemo.de/win98/ More specifically http://oerg866.titandemo.de/win98/files/AutoPatcher98.Dec07.Final.exe

As a programmer, I actually checked first if this is even possible, and I also noticed that the function fills a buffer, so no, kstub is useless here. What I've been trying to figure out, is how to implement such functions myself, i.e. make a simple dll with a function called GetLogicalProcessorInformation and return a preset buffer (Gathered friom debugging and capturing the buffer on an xp installation and figuring out what it does) that the program would only gather from that one CPU core is available and nothing else: ProcessorMask = 1, ProcessorCore = 0, NumaMode = nothing, Cache_Descriptor = 0... Unfortunately no kernel extension projects seem to have such a simple way of doing that....

Thanks, mate! So far so good. But I'm afraid I've hit a brick wall, now it wants Kernel32:GetLogicalProcessorInformation, which seems to not be supported by anything.... what now? :S (PS: The game I'm trying to run is PES2014 ) The game itself seems to be a lot less of a hassle, the program that allows you to change controller settings etc is a .NET 4.0 program... but I can copy settings from my main computer

Huh? Oh, that's... odd, I'm sure I set it to that yesterday.... I'll try again later. Thanks! Oh, on the subject, if a game wants d3dx9_43.dll, Can I just rename an older dll or can I just use this dll? I haven't looked at directx-based software in ages....

Hi, I'm looking for a stub for KERNEL32.DLL:VerSetCondidtionMask reporting as Windows XP, please?

If you can, disable all IDE ports, that will usually get it going (albeit losing all IDE functionality)

.... trolling?? any USB device should be up and running in half that or even less...

Basically, the goal is to fix this bug that prevents one from making a huge pack of drivers. This is probably very interesting for people collecting and testing old hardware.

Yes, exactly. And I think if I keep reading submix8c's posts I will have a heart attack

For example, to make a Windows installation that is preloaded with a lot of drivers, so you won't have to find them manually

Oh, shh There is not a definitive answer, of course. It depends on how many PnP IDs an INF adds to the system. Here is a random bundle of INFs that will generate a >2MB DRVIDX.BIN. Transfer it to a windows 98 installation and set HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion, OtherDevicePath to where you unpack them (in my case "C:\W\D") and let windows rebuild its driver database. It should do that automatically, if it doesn't you need to delete C:\WINDOWS\INF\*.bin. http://oerg866.titandemo.de/f/random_infs.zip

Hi, as for some reason nobody believes me when I say Win9x does have a 2MB DRVIDX.BIN limit (yes, it's true, try it yourself by bombarding windows with tons of extra INF files...), I decided to investigate this issue myself, rather than waiting for someone else to patch it The first step was to get a general idea of what this format looks like. Here's what I was able to come up with. Excuse the crudeness, it's 8AM and I haven't slept yet drvidx.bin layoutNote: short means 16-bit integer and int means 32-bit integer.char* means '\0'-terminated string.Header:0x0 short 61 6E Magic number, always starts with this0x2 int amount of entries in this index file0x6-0xf ????After the header there are all the entries, one after another.The first entry is located at offset 0x10.An entry consists of these attributes:short total size of this entry in bytesint pointer to the PnP ID stringint pointer to the device class stringint pointer to the device name stringint pointer to the hardware vendor stringint pointer to the driver vendor stringint pointer to the end of the string data(the above pointers are relative to the start of the entry, including the header)int number of this entry in the fileint unknown (version??)int Offset in DRVDATA.BIN at which the information corresponding to this entry is located (see below for details)-----dosdate file date of the driver. It is a two-byte date format from MS.Format description from MSDN:Bits Description0-4 Day of the month (1–31)5-8 Month (1 = January, 2 = February, and so on)9-15 Year offset from 1980 (add 1980 to get actual year)Some examples (remember, little endian)97 26 = 23 April 1999 (Win98SE RTM date)BD 40 = 29 May 2012 (This was a VMware driver )-----char* Device identifier (PnP ID)char* Device Classchar* Device Namechar* Hardware Vendorchar* Driver vendorint always 0========================================================drvdata.bin layoutThere is no header, all the entries are next to each other.An entry looks like this:short length of this entryshort offset in entry of INF-file name stringint always 0dosdate same as in DRVIDX.BINint pointer to string containing the section that defines this entry in the specified INF fileshort unknownchar* INF file namechar* INF section nameI have started disassembling SETUPX.DLL and found some promising leads. If the stars align, I might have a patch ready by this weekend

ahh, sorry, this one was caused by my own idiocy, I did some stuff with system.ini before the drivers and restored a back up after that, not realizing it of course. Sorry, my fault

This was tested on 4 machines. The system was installed with my ISO. Windows was fully functional until I installed SP3. The hardware involved was completely unrelated (AMD K5, i430TX, Number Nine Revolution 3D vs. Intel P3 550, VIA Apollo 133, Geforce 2 GTS)... The SP3 files were unaltered. I installed them manually, even to test. They still broke the resolution....

Hi, I think USP 3.33 has a bug. After installing the SP, screen resolution reverts to 640x480, 16 colors, and it can only be fixed by re-installing the VGA drivers.... did anyone else notice this?

Failure-Prone? How so? 1) MSBatch line: HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion","OtherDevicePath",,"C:\WINCD\d\" 2) Installation from ISO is done with a snapshot of the HDD taken during the first reboot. The installation as a base was conducted with SETUP /is /p i MSBATCH.INF. It's aimed at newer computers. They tend to work better with APM mode, so that's why I used that... 3) Directory structure of C:\: DIR: PROGRA~1 DIR: W DIR: WINDOWS 4) W is an important directory: 05.05.2014 16:02 <DIR> D05.05.2014 16:02 <DIR> DIRECTX05.05.2014 16:02 <DIR> DRVMGMT05.05.2014 16:02 <DIR> NUSB05.05.2014 16:02 <DIR> SUPP05.05.2014 16:02 <DIR> U98SESP323.04.1999 21:22 168.960 BASE4.CAB23.04.1999 21:22 1.802.240 BASE5.CAB23.04.1999 21:22 191.747 BASE6.CAB23.04.1999 21:22 274.460 CATALOG3.CAB23.04.1999 21:22 14.451 CHL99.CAB23.04.1999 21:22 496 DELTEMP.COM23.04.1999 21:22 85.050 DOSSETUP.BIN23.04.1999 21:22 1.462.272 DRIVER11.CAB23.04.1999 21:22 1.802.240 DRIVER12.CAB23.04.1999 21:22 1.802.240 DRIVER13.CAB23.04.1999 21:22 1.802.240 DRIVER14.CAB23.04.1999 21:22 1.802.240 DRIVER15.CAB23.04.1999 21:22 1.802.240 DRIVER16.CAB23.04.1999 21:22 1.802.240 DRIVER17.CAB23.04.1999 21:22 1.802.240 DRIVER18.CAB23.04.1999 21:22 1.802.240 DRIVER19.CAB23.04.1999 21:22 1.796.408 DRIVER20.CAB23.04.1999 21:22 93.242 EXTRACT.EXE23.04.1999 21:22 49.575 FORMAT.COM23.04.1999 21:22 6.594 INTL.TXT23.04.1999 21:22 686.042 MINI.CAB04.05.2014 03:32 8.038 MSBATCH.INF23.04.1999 21:22 339.473 NET10.CAB23.04.1999 21:22 1.610.240 NET7.CAB23.04.1999 21:22 1.802.240 NET8.CAB23.04.1999 21:22 1.802.240 NET9.CAB23.04.1999 21:22 3.270 OEMSETUP.BIN23.04.1999 21:22 78.720 OEMSETUP.EXE23.04.1999 21:22 1.331.200 PRECOPY1.CAB23.04.1999 21:22 1.335.443 PRECOPY2.CAB23.04.1999 21:22 920 SAVE32.COM23.04.1999 21:22 143.818 SCANDISK.EXE23.04.1999 21:22 995 SCANDISK.PIF23.04.1999 21:22 4.438 SCANPROG.EXE23.04.1999 21:22 165.502 SCANREG.EXE23.04.1999 21:22 5.712 SETUP.EXE23.04.1999 21:22 52.294 SETUP.TXT23.04.1999 21:22 439.824 SETUP0.WAV23.04.1999 21:22 14.924 SETUP1.WAV23.04.1999 21:22 14.992 SETUP2.WAV23.04.1999 21:22 45.379 SMARTDRV.EXE23.04.1999 21:22 229.680 SUBACK.BIN23.04.1999 21:22 77.824 SUCATREG.EXE23.04.1999 21:22 1.472 SUHELPER.BIN23.04.1999 21:22 168.096 W98SETUP.BIN23.04.1999 21:22 537 WB16OFF.EXE23.04.1999 21:22 5.632 WIN98_21.CAB23.04.1999 21:22 1.802.240 WIN98_22.CAB (....)23.04.1999 21:22 1.056.537 WIN98_74.CAB23.04.1999 21:22 1.708.985 WIN98_OL.CAB23.04.1999 21:22 14.144 XMSMMGR.EXE(BTW: It's all working fine now, as DRVIDX.BIN is below 2MB. What you do not realize is: this file has ALL PnP IDs Windows Knows from all INFs in C:\WINDOWS\INF and OtherDevicePath contains!) 5) SUPP contains a lot of support scripts to install stuff... Installing of Servicepack 3.33 is done automagically, as well as NUSB 3.6E and DirectX 9.0c so far 6) DRVMGMT is a special project I'm ready to release soon. See here: https://www.youtube.com/watch?v=0D8e0TgYT_g 7) D contains the drivers. It's not like the "DriverPacks". All INFs reside in this directory. I might make an in depth explanation on how this folder is created but it is very complicated and you don't seem to (want to) understand what I'm saying about it, so I won't bother (for now, at least) The INFs have been prepared to reference all files (standardized [sourceDisksNames] section!!) in an appropriate .CAB file that is inside that directory. This process is fully supported by windows 98 and works perfectly. 8) The ISO has all of these files written in a large binary blob written to the hard disk by an installer (better for sequential reading off a CD-ROM drive). I wrote this installer using C++ (DJGPP 2.04). As you can tell, I've put a lot of effort into this and unfortunately at this point the technicalities are just too far in-depth, so your simplistic approaches don't help anymore. Thanks for everything so far though, you helped me solve the initial problem of getting to add drivers! I'd be happy to get back into debugging things to assist rloew in tracking down the problem, btw. BTW, I wish I could release all of this, but the legality is questionable ... :/ I could of course release the program I wrote to prepare all the INF files with a small tutorial. Maybe I'll do that soon, eh?

Relax, this has nothing to do with UBCD I have now modified my INF preparation tool to modify SourceDisksNames instead of SourceDisksFiles, because some INFs (e.g.NVIDIA 82.69) dont actually declare alll the files (the NVAML.INF only declares NVAML.INF as its only file, wtf??) and windows can't find them. I compressed all driver files that aren't INFs into CABs using MakeCab and modify the SourceDiskNames like this: 2 = 1="SiSAGPDriverDiskforWindows",,0putting 1="SiSAGPDriverDiskforWindows",D\c0.cab,0 That way I save a lot of space too, made the ISO shrink to CD size again

OK, where do I start... No Yeah, well.... I have a custom ISO with a custom installer I wrote that copies a snapshot of files after first setup step to the hard disk.. No black magic here, yet. My folder for the drivers I have prepared has all the drivers in the subfolders, in their original state: My tool INFPREP.EXE scans all those folders for INF files, and modifies the SourceDisksFiles part like this: Original: sis597m.drv=1 sis597m.vxd=1 After modding: sis597m.drv=1,D\G4 sis597m.vxd=1,D\G4 The inf files all get an unique number and get put in the ROOT dir of the drivers ("D\"), which is what OtherDevicePath points to. When windows builds its driver database, all of those INFs get scanned and added to DRVIDX.BIN, an index of PNPIDs with their names that it has drivers for. Since I have a LOT more drivers in here than you do in your UBCD, this file gets above 2MB, hence the crash. Is it more clear now? Directory of F:\temp\98SE-PLUS\WINCD\DRIVER04.05.2014 08:03 17.447 0.inf04.05.2014 08:03 11.724 1.inf04.05.2014 08:03 1.507 10.inf04.05.2014 08:03 5.913 100.inf04.05.2014 08:03 41.104 101.inf04.05.2014 08:03 3.659 102.inf04.05.2014 08:03 17.474 103.inf04.05.2014 08:03 1.888 104.inf04.05.2014 08:03 4.773 105.inf04.05.2014 08:03 14.821 106.inf04.05.2014 08:03 2.407 107.inf04.05.2014 08:03 3.846 108.inf04.05.2014 08:03 791 109.inf04.05.2014 08:03 1.888 11.inf04.05.2014 08:03 8.886 110.inf04.05.2014 08:03 22.527 111.inf04.05.2014 08:03 1.807 112.inf04.05.2014 08:03 3.440 113.inf04.05.2014 08:03 4.937 114.inf04.05.2014 08:03 3.086 115.inf04.05.2014 08:03 4.484 116.inf04.05.2014 08:03 3.915 117.inf04.05.2014 08:03 2.922 118.inf04.05.2014 08:03 1.601 119.inf04.05.2014 08:03 2.431 12.inf04.05.2014 08:03 4.712 120.inf04.05.2014 08:03 3.939 121.inf04.05.2014 08:03 54.478 122.inf04.05.2014 08:03 12.203 123.inf04.05.2014 08:03 36.907 124.inf04.05.2014 08:03 21.480 125.inf04.05.2014 08:03 18.871 126.inf04.05.2014 08:03 23.539 127.inf04.05.2014 08:03 27.414 128.inf04.05.2014 08:03 19.157 129.inf04.05.2014 08:03 2.841 13.inf04.05.2014 08:03 15.899 130.inf04.05.2014 08:03 2.368 131.inf04.05.2014 08:03 18.668 132.inf04.05.2014 08:03 15.412 133.inf04.05.2014 08:03 4.681 134.inf04.05.2014 08:03 25.696 135.inf04.05.2014 08:03 36.781 136.inf04.05.2014 08:03 17.797 137.inf04.05.2014 08:03 4.922 138.inf04.05.2014 08:03 4.944 139.inf04.05.2014 08:03 28.753 14.inf04.05.2014 08:03 4.330 140.inf04.05.2014 08:03 5.295 141.inf04.05.2014 08:03 30.569 142.inf04.05.2014 08:03 5.985 143.inf04.05.2014 08:03 6.524 144.inf04.05.2014 08:03 36.781 145.inf04.05.2014 08:03 6.757 146.inf04.05.2014 08:03 49.341 147.inf04.05.2014 08:03 33.397 148.inf04.05.2014 08:03 46.490 149.inf04.05.2014 08:03 2.130 15.inf04.05.2014 08:03 45.303 150.inf04.05.2014 08:03 28.559 151.inf04.05.2014 08:03 62.247 152.inf04.05.2014 08:03 12.058 153.inf04.05.2014 08:03 48.280 154.inf04.05.2014 08:03 40.060 155.inf04.05.2014 08:03 17.890 156.inf04.05.2014 08:03 11.135 157.inf04.05.2014 08:03 15.113 158.inf04.05.2014 08:03 8.679 159.inf04.05.2014 08:03 54.012 16.inf04.05.2014 08:03 4.451 160.inf04.05.2014 08:03 12.117 161.inf04.05.2014 08:03 6.325 162.inf04.05.2014 08:03 6.816 163.inf04.05.2014 08:03 28.522 164.inf04.05.2014 08:03 47.957 165.inf04.05.2014 08:03 10.780 166.inf04.05.2014 08:03 513 167.inf04.05.2014 08:03 18.536 168.inf04.05.2014 08:03 39.623 169.inf04.05.2014 08:03 26.238 17.inf04.05.2014 08:03 757 170.inf04.05.2014 08:03 4.538 171.inf04.05.2014 08:03 13.993 172.inf04.05.2014 08:03 2.095 173.inf04.05.2014 08:03 25.149 174.inf04.05.2014 08:03 2.733 175.inf04.05.2014 08:03 2.569 176.inf04.05.2014 08:03 1.672 177.inf04.05.2014 08:03 3.662 178.inf04.05.2014 08:03 2.313 179.inf04.05.2014 08:03 20.481 18.inf04.05.2014 08:03 1.248 180.inf04.05.2014 08:03 3.246 181.inf04.05.2014 08:03 45.551 182.inf04.05.2014 08:03 13.108 183.inf04.05.2014 08:03 21.639 184.inf04.05.2014 08:03 1.537 185.inf17.07.2008 09:55 40.480 186.inf04.05.2014 08:03 2.648 19.inf04.05.2014 08:03 75 2.inf04.05.2014 08:03 49.706 20.inf04.05.2014 08:03 30.715 21.inf04.05.2014 08:03 16.205 22.inf04.05.2014 08:03 2.914 23.inf04.05.2014 08:03 2.127 24.inf04.05.2014 08:03 6.072 25.inf04.05.2014 08:03 44.039 26.inf04.05.2014 08:03 12.936 27.inf04.05.2014 08:03 20.755 28.inf04.05.2014 08:03 5.237 29.inf04.05.2014 08:03 13.023 3.inf04.05.2014 08:03 23.093 30.inf04.05.2014 08:03 34.940 31.inf04.05.2014 08:03 29.594 32.inf04.05.2014 08:03 4.466 33.inf04.05.2014 08:03 3.527 34.inf04.05.2014 08:03 2.436 35.inf04.05.2014 08:03 956 36.inf04.05.2014 08:03 521 37.inf04.05.2014 08:03 8.623 38.inf04.05.2014 08:03 14.751 39.inf04.05.2014 08:03 13.526 4.inf04.05.2014 08:03 8.379 40.inf04.05.2014 08:03 6.034 41.inf04.05.2014 08:03 13.669 42.inf04.05.2014 08:03 3.007 43.inf04.05.2014 08:03 24.316 44.inf04.05.2014 08:03 29.630 45.inf04.05.2014 08:03 18.852 46.inf04.05.2014 08:03 578 47.inf04.05.2014 08:03 34.052 48.inf04.05.2014 08:03 46.499 49.inf04.05.2014 08:03 53.945 5.inf04.05.2014 08:03 9.947 50.inf04.05.2014 08:03 3.012 51.inf04.05.2014 08:03 9.932 52.inf04.05.2014 08:03 11.902 53.inf04.05.2014 08:03 12.214 54.inf04.05.2014 08:03 11.980 55.inf04.05.2014 08:03 12.058 56.inf04.05.2014 08:03 11.824 57.inf04.05.2014 08:03 11.808 58.inf04.05.2014 08:03 42.693 59.inf04.05.2014 08:03 22.987 6.inf04.05.2014 08:03 27.125 60.inf04.05.2014 08:03 7.383 61.inf04.05.2014 08:03 14.043 62.inf04.05.2014 08:03 1.153 63.inf04.05.2014 08:03 8.643 64.inf04.05.2014 08:03 6.648 65.inf04.05.2014 08:03 3.784 66.inf04.05.2014 08:03 8.233 67.inf04.05.2014 08:03 7.930 68.inf04.05.2014 08:03 4.982 69.inf04.05.2014 08:03 37.386 7.inf04.05.2014 08:03 809 70.inf04.05.2014 08:03 615 71.inf04.05.2014 08:03 803 72.inf04.05.2014 08:03 9.257 73.inf04.05.2014 08:03 4.914 74.inf04.05.2014 08:03 3.149 75.inf04.05.2014 08:03 3.570 76.inf04.05.2014 08:03 1.362 77.inf04.05.2014 08:03 1.474 78.inf04.05.2014 08:03 48.709 79.inf04.05.2014 08:03 12.695 8.inf04.05.2014 08:03 4.809 80.inf04.05.2014 08:03 7.805 81.inf04.05.2014 08:03 48.545 82.inf04.05.2014 08:03 5.222 83.inf04.05.2014 08:03 50.203 84.inf04.05.2014 08:03 5.282 85.inf04.05.2014 08:03 10.719 86.inf04.05.2014 08:03 3.183 87.inf04.05.2014 08:03 4.329 88.inf04.05.2014 08:03 2.204 89.inf04.05.2014 08:03 38.915 9.inf04.05.2014 08:03 5.145 90.inf04.05.2014 08:03 2.344 91.inf04.05.2014 08:03 1.220 92.inf04.05.2014 08:03 11.922 93.inf04.05.2014 08:03 8.563 94.inf04.05.2014 08:03 54.436 95.inf04.05.2014 08:03 51.432 96.inf04.05.2014 08:03 47.452 97.inf04.05.2014 08:03 65.070 98.inf04.05.2014 08:03 19.120 99.inf 187 File(s) 2.975.114 bytes 0 Dir(s) 317.873.094.656 bytes free

Pardon me, rloew, I meant FileMon of course. Got confused there, I guess... I cannot really tell all the details, but the crash appears to happen whenever it enumerates a device, both during Setup and in the "update driver"-wizard. During setup the white error box that pops up references MSGSVR32, the other one is about rundll... Not sure how much that helps.. rundll generally shouldn't touch drvidx.bin, because rundll just calls DLLs... It would appear that SETUPX. DLL is the culprit because that is the file actually providing the code for this... Excuse all the typoes, it's 7AM and I haven't slept yet Yep, exactly what I'm trying to do... I have a 400GB driver archive at hand being put into use (not all of it of course )