buyerninety Posted May 4, 2014 Share Posted May 4, 2014 In post #28, Drugwash states he has noticed:Edit: just seen setupx.dll being called in a lot of infs through rundll.exe in the form:StubPath = "rundll.exe %11%\setupx.dll, InstallHinfSection [...]" Reference;http://support.microsoft.com/kb/164787"Rundll command lineThe command line for Rundll is as follows:RUNDLL.EXE <dllname>,<entrypoint> <optional arguments> An example is as follows:RUNDLL.EXE SETUPX.DLL,InstallHinfSection 132 C:\WINDOWS\INF\SHELL.INF There are 3 issues to consider carefully"......"3. In the above command line,"..."there cannot be any white spaces in between the <dllname>, the comma, and the <entrypoint> function." Link to comment Share on other sites More sharing options...
Drugwash Posted May 4, 2014 Share Posted May 4, 2014 My bad, got a habit of always inserting a blank space after the comma. Anyway, the idea was merely to point out that setupx.dll is being run through rundll.exe. Thanks for the correction though, someone might have accidentally followed the bad command formatting. Link to comment Share on other sites More sharing options...
submix8c Posted May 4, 2014 Share Posted May 4, 2014 (edited) Fixing another typo -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......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 )That would be MSGSRV32 and I suspected as much. I also suspected you were attempting an AIO when I seen MULTIPLE folder-names of the SAME TYPE HARDWARE. I can tell you this - I have NO CLUE what/how you INSTALLED! AGAIN, Using the UBCD -and- that EXACT MSBATCH I linked to -and- on the UBCD those EXACT DRIVER PACKS, absolutely NONE of the "extra" INF's showed up in the INF folder and -only- several of them into the INF\OTHER folder. FYI, the PROCEDURE that's used in the UBCD scenario ASSUMES a CLEAN INSTALL onto a PRE-FORMATTED FAT32 (using DEFAULTS) -and- COPYING the WHOLE SHEBANG onto HDD -and- using THIS setup command from DOS (i.e. a WIN98SE EBD -or- CD-Boot-Image).SETUP.EXE /ie /im /iq /is /it /m /nf /nh /nm /nr /nxYou're not giving complete info except in bits and pieces. It would be REAL nice if you provided what I asked for - something is amiss! BTW, the OEM procedure (not generally available to the public) was NEVER intended as an AIO, but rather for a SPECIFIC set of machines by which CLONING was used along with the Win9x OEM Preinstall Kit (also not generally available - EVER). SO... try a CLEAN install using the UBCD "method". You -must- be doing something wrong! BTW, in your BIOS, do you have "PnP OS" set (just curious)? AFAICT, only thos PnP Hardware items should be "installed" DIRECTLY FROM the Setup Folders via that Paramter you will NOT show (in MSBATCH.INF)! If those folders DISAPPEAR (i.e. deleted) -and- you were to delete any Hardware THAT PHYSICALLY EXISTS within them -and- delete DRVIDX/DRVDATA BIN files -and- reboot -and cause Hardware Detect to occur, they will NOT be found (WITH the UBCD procedure). I am BETTING you're "copying" the INF's to the INF folder somehow (PLEASE tell me I'm wrong)... HTH edit - FYI, many "fixes" are added during UBCD98 Setup, and not Post-Setup, unlike USP98. Edited May 4, 2014 by submix8c Link to comment Share on other sites More sharing options...
oerg866 Posted May 4, 2014 Author Share Posted May 4, 2014 (edited) OK, where do I start... I am BETTING you're "copying" the INF's to the INF folder somehow (PLEASE tell me I'm wrong)... No I can tell you this - I have NO CLUE what/how you INSTALLED! AGAIN, Using the UBCD -and- that EXACT MSBATCH I linked to -and- on the UBCD those EXACT DRIVER PACKS, absolutely NONE of the "extra" INF's showed up in the INF folder and -only- several of them into the INF\OTHER folder. FYI, the PROCEDURE that's used in the UBCD scenario ASSUMES a CLEAN INSTALL onto a PRE-FORMATTED FAT32 (using DEFAULTS) -and- COPYING the WHOLE SHEBANG onto HDD -and- using THIS setup command from DOS (i.e. a WIN98SE EBD -or- CD-Boot-Image). 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: Directory of F:\temp\98SE-PLUS\WINCD\DRIVER04.05.2014 19:21 <DIR> .04.05.2014 19:21 <DIR> ..04.05.2014 08:03 <DIR> a004.05.2014 08:03 <DIR> a104.05.2014 08:03 <DIR> a204.05.2014 08:03 <DIR> a304.05.2014 08:03 <DIR> a404.05.2014 08:03 <DIR> a504.05.2014 08:03 <DIR> a604.05.2014 19:18 <DIR> c004.05.2014 08:03 <DIR> g004.05.2014 08:03 <DIR> g104.05.2014 08:03 <DIR> g204.05.2014 08:03 <DIR> g304.05.2014 08:03 <DIR> g404.05.2014 08:03 <DIR> g504.05.2014 08:03 <DIR> g604.05.2014 08:03 <DIR> l004.05.2014 08:03 <DIR> r004.05.2014 08:03 <DIR> r104.05.2014 08:03 <DIR> r204.05.2014 08:03 <DIR> r304.05.2014 08:03 <DIR> U0 0 File(s) 0 bytes 23 Dir(s) 317.873.094.656 bytes free My tool INFPREP.EXE scans all those folders for INF files, and modifies the SourceDisksFiles part like this: Original:sis597m.drv=1sis597m.vxd=1 After modding: sis597m.drv=1,D\G4sis597m.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 Edited May 4, 2014 by oerg866 Link to comment Share on other sites More sharing options...
submix8c Posted May 4, 2014 Share Posted May 4, 2014 You're on your own. You've gone completely out of bounds of what I gave you and haveYeah, 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:Directory of F:\temp\98SE-PLUS\WINCD\DRIVER 04.05.2014 19:21 <DIR> .04.05.2014 19:21 <DIR> ..04.05.2014 08:03 <DIR> a0Directory of F:\temp\98SE-PLUS\WINCD\DRIVER04.05.2014 08:03 17.447 0.infNow about those additional INF files (second list) - You're force-installing them? There is NO REASON that they should exist, AFAICT. The other part that "doesn't fit" is thisMy tool INFPREP.EXE scans all those folders for INF files, and modifies the SourceDisksFiles part like this: Original:sis597m.drv=1sis597m.vxd=1 After modding: sis597m.drv=1,D\G4sis597m.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.How does "DRIVERS" = "D" I have no clue. Guess you didn't pay attention to that. With the Path Pointers, the Structure SHOULD be -x:\WIN98 - win98 files + msbatch.inf + driver-foldersx:\WIN98\D - general Drivers Folderx:\WIN98\D\1 - example "group" folder#1, which MAY have Driver Files, along with corresponding INF's -or- just INF'sx:\WIN98\D\1\FILES1 - Driver Files for "just INF's" from above directory.Can I assume that you DID download the Driver Packs and EXPAND them into the "D-folder" (numbered 1-6) and look in the filders/inf's AND revisit my sample msbatch.inf? "Custom Installer"? OK, fine. BUT the UBCD is STRICTLY BAT scripts following the OEM Install Standards. You are not doing that. Indeed, there is NO "magic" or "custom" ANYTHING in a Basic Install. I will NOT provide UBCD to prove it to you, as the thread has been REMOVED for MSFN reasons (some software was considered warez, e.g. GDISK, and some was not properly listing Freeware Licensed)! AGAIN, there's something else you MUST be doing, since I don't have the "size problem" that you have. NO WAY that an "unused driver" should appear there UNLESS you are FORCING it into the Driver Database. ANY file from an OEM Install MAY get into the INF Folder and Hardware Database IF it exists and WILL show up as an "OEMnnn.INF/PNF" and MAY get copied into the "INF\OTHER" Folder - at first reboot. I have ATM TWO Installs using my UBCD and NETHER exhibit the "symptoms" you have. Defunct Topic Link (and not archived anywhere) -http://www.msfn.org/board/Unattended-Boot-CD-Windows-98-98SE-46-t88008.htmlI know for a fact something's fishy in you're setup procedures since I was a prime participant.Where it apparently started -http://www.msfn.org/board/topic/49892-unattended-and-updated-boot-cd-for-windows-98/ INFINST.EXE (maybe you tried using it outside of the given UBCD OEM method?) -http://web.archive.org/web/20090414214449/http://support.microsoft.com/kb/169539ftp://ftp.microsoft.com/services/technet/samples/ps/win98/reskit/INFINST/README.TXTThis link - http://technet.microsoft.com/en-us/library/cc750055.aspx#XSLTsection124121120120From this link - http://www.msfn.org/board/topic/149231-trying-to-use-infinst-to-add-drivers-to-win-98-install/If that's what you're doing, you're doing it non-OEM and trying a "deploy" style. AGAIN, ONLY basic BAT scripts, no "special" INF's other than Manually Modded Driver Inf's and the MSBATCH.INF. Nocustom magic" at all. BTW, the MSBATCH.INF was "manually" created because of so much "missing" MS Info (ONLY for OEM's). We gleaned ever bit of it from the WWW, samples, other OEM Installs, and experimentation. We did NOT use "BATCH98" because it is INCOMPLETE! Have fun with your monster AIO-Drivers / DRVIDX.BIN! (Shhhh, it's a SECRET!) Link to comment Share on other sites More sharing options...
oerg866 Posted May 5, 2014 Author Share Posted May 5, 2014 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 Link to comment Share on other sites More sharing options...
submix8c Posted May 5, 2014 Share Posted May 5, 2014 Heh...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 suppose you didn't notice that there is a SETUP.EXE and several CAB files? Didn't you notice I specifically stated DRIVERS ONLY? It's installed via InstallShield. I have no time right now to explain this "anomaly" - you figure it out (or I'll -try- to later). Additionally, well DUH! I didn't say it DID have anything to do with UBCD, but I -did- say your methods leave a lot to be desired (and a failure-prone), since UBCD is (to paraphrase) very SIMPLE in its implementation. You have this "I won't tell you, so use your crystal ball" mentality - mine is currently broken. Off to get fitted for new chompers... Link to comment Share on other sites More sharing options...
jaclaz Posted May 5, 2014 Share Posted May 5, 2014 (edited) You have this "I won't tell you, so use your crystal ball" mentality - mine is currently broken. Additionally I am told that you will fail to pay for your yearly subscription to the "Clarvoyant Assistance Club", so you won't have support by their specialized technician to fix it. jaclaz Edited May 5, 2014 by jaclaz Link to comment Share on other sites More sharing options...
submix8c Posted May 5, 2014 Share Posted May 5, 2014 HAH!(the NVAML.INF only declares NVAML.INF as its only file, wtf??)Better open that INF file and look closely at the contents. EVERYTHING is there under an ENTIRELY different Section. Your "custom INF modify EXE program" is broken! Link to comment Share on other sites More sharing options...
oerg866 Posted May 5, 2014 Author Share Posted May 5, 2014 (edited) 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~1DIR: WDIR: 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? Edited May 5, 2014 by oerg866 Link to comment Share on other sites More sharing options...
submix8c Posted May 5, 2014 Share Posted May 5, 2014 (edited) HAHAHAHAH! The "expert" speaks! 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)EXACTLY like UBCD DriverPacks! YOU don't seem to realize that the Self-Extracting RAR files are extracted (via a BAT during the Copy Over To HDD phase) EXACTLY to "D\1" (for e.g. Pack1) just like your "unique" method. You're not doing anything "special". 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! You ARE aware that there are MANY C++ programmers here (including jaclaz, I believe), so you're not "special" in that regard. We even know (shhhh) ASM. Now, about the nVidia Driver Package - did you notice what I said above or are you completely ignoring me? Oh, I know - you read it and then claim you "solved" it all by yourself! "Automagically", as in RunOnce? AutoIT? You DO realize that several of us have many (as in decades) more experience and knowledge than "some experts". Rest easy, your "secrets" are safe with MSFN. Edited May 5, 2014 by submix8c Link to comment Share on other sites More sharing options...
jaclaz Posted May 5, 2014 Share Posted May 5, 2014 You ARE aware that there are MANY C++ programmers here (including jaclaz, I believe), so you're not "special" in that regard. We even know (shhhh) ASM. Well, don't count on me for C, C++ or C# (the one I call C dumb). I am NOT a programmer, I write only (usually half-@§§ed ) batch scripts, usually for CMD.EXE, sometimes for grub4dos.(which doesn't really mean that I cannot put together -if really-really *needed* a C program, or even make it very, very, very small - though admittedly there are people far better than me at it ) Example (completely OT , but JFYI):http://reboot.pro/topic/18792-if-anyone-is-up-for-a-challenge/ jaclaz 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now