submix8c

Additionally, which OS? You've posted about Windows XP also Windows 7 (as refurbisher with references to WPI license, usage, etc.). You also (at one time) got "shot down" over trying to combine some ISO files (torrented). Even so, it's possible to Slipstream with the correct tools in either one -or- install via UnattendXML+CMDscript (Windows 7). XP is slightly different, in that -some- updates only apply -if- a given component is installed (see http://xdot.tk/#fn3). HTH

This? (not sure how accurate, but -appears- to be...) http://en.wikipedia.org.advanc.io/wiki/File_Allocation_Table Bear in mind, a badly written Installer -or trojan/virus/whatever- could (theoretically) screw up a directory entry regardless. In this case we can "assume" that the OP simply has used something that is not suited to their CodePage/Language (?) thus the "weird" characters. (- need a whole bunch of emoticon links - anyone up to making a list?) edit - emoticons - get the link to image above, start with "1.gif", up to "79.gif"... guess you just have to "browse"? <= me sometimes.

HAH! 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!

Heh... 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...

http://www.msfn.org/board/forum/93-windows-post-install-wizard-wpi/ Windows Post-Install Wizard (WPI) - WPI is a hypertext application designed to give users choice of app-install Basically -any- Application Software that you can find and utilize Silent Install techniques. http://www.wpiw.net/index.htmlGenerally, WPIW isn't used for Windows Updates since other methods are used. Maybe you're attempting to use it in a similar fashion to AutoPatcher? Notice there are -many- REG Entries and/or Files that may need checked to "update" a pre-Updated (already installed some MS Updates) to prevent re-install (what AutoPacther does). This is (generall) wht you would need to do with WPIW, including Application Software (don't attempt to install TWICE). True?http://www.wpiw.net/help.html Scroll down to "Automated Software Installation" -http://www.stylight.com/Engineering/automating-client-pc-deployment-using-serva-and-the-windows-post-installation-wizard/ WPIW is not -necessarily- intended to be used as an AutoPatcher Replacement, but rather a PostInstall/Update Applications Installer (big difference between Install+Update and Installing an AddOn, which WPIW is intended to be used for). edit - also see here, with direct reference to a number of MSFN Topics.http://www.symantec.com/connect/articles/scripted-os-install-part-7-installing-software HTH

"Cloud Computing"... I abhor "the cloud" as it's someone else' HDD's running apps on someone else' server. Does noone understand what "the cloud" is? http://www.pcmag.com/article2/0,2817,2372163,00.asp No thank you very much. That includes the "latest" rage of Outlook "in the cloud" (basically Yahoo, Google, etc.). I keep mine on my OWN pc! BTW, did you note the mention of keeping your AV up to date? Laughable, since there's already a topic on that as to WHO will support XP AV after EOS.

:doh: <= new emoticon? "Theoretically" that should (normally) work -unless- the long-name is (e.g.) already 8.3 and the short-name is currupted as well. (note that there are actually TWO entries AFAICR for LFN support.)

Newer Updates all look like that when "unzipped". The "old way" is no longer used. The Extract process is different even (in order to get the real files).

Well then, it seems like a pointless exercise to "extract" since rloew basically said "trade secret". Guess the OP is determined to extract rather than use the pre-supplied. 'Bye now...

You're on your own. You've gone completely out of bounds of what I gave you and have Now 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 this 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-folders x:\WIN98\D - general Drivers Folder x:\WIN98\D\1 - example "group" folder#1, which MAY have Driver Files, along with corresponding INF's -or- just INF's x:\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.html I 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/169539 ftp://ftp.microsoft.com/services/technet/samples/ps/win98/reskit/INFINST/README.TXT This link - http://technet.microsoft.com/en-us/library/cc750055.aspx#XSLTsection124121120120 From 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. No custom 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!)

As I said, we will need the exact VEN\DEV string, since I can't find that info stored on my HDD (my brother has that model w/XP). The XP INF has a LOAD of VEN\DEV specs and OLDER versions don't have all of them. HKLM\PCI\VEN_nnnn&DEV_nnnn(etc...) in the Registry of the WinME should help if you want to pursue it. It'll free up a PCI slot... edit - it would also be nice if you specified -which- Driver File works on WinME.

Hmmm... "Scary" thought, but I played with this before (I have a copy floating around somewhere from an old HDD) -but- it's DOS-oriented. http://en.wikipedia.org/wiki/PC_Tools_%28Central_Point_Software%29 EDIT! And here is Starman's take on a Disk Editor (appears to be an "upgraded" CP Disk Editor) - http://thestarman.narod.ru/DOS/bd98/SD1.htm I will -not-swear to it but it -may- be useful -and very dangerous-!!! (note I found my Norton Utilities disk for Win95, so mine is "in between" the one that the above link talks about.)

The comments were not to disagree with your analyses, but with the FUD related to the Article implying that they don't even EXIST in XP, which is a flat-out lie! specifically DEP and UAC. It appears to blatantly attempt to convince the Common User that those facilities don't exist. Remember, OEM's by DEFAULT set a First User up as Administrator and (as you stated) DEP is an OptIn, even in the BIOS (hardware DEP).

??? Why are you bothering when you have it already? Helpful hint - it's an Animated BMP (it "scrolls" at the bottom) so it MAY be possible that the "scroll" part is put "somewhere else" ...

Fixing another typo - 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.

SoundBlaster Live! will be just fine. Your Built-In sound is an ADI SoundMax and it's also a 5.1 (AFAICT) - specifically an "ADI 1980" Controller. XP-and-up drivers (just to know what it has) - http://ftp.dell.com/Pages/Drivers/dimension-4600.html#Audio If it has a SATA drive you -may- not be able to set it to PATA-mode, but I may be mistaken and it's already "defaulted" to it. It does, however have two PATA connectors (primary/secondary) in addition to the two SATA-I (150) connectors. This may-or-may-not be a good driver. We'll need the exact VEN/DEV info. http://www.dell.com/support/drivers/us/en/19/driverdetails?driverid=R46202 Manuals - http://www.dell.com/support/home/us/en/19/product-support/product/dimension-4600/manuals?c=us Looking for where I got the (better) Service Manual now... FWIW, here it is Online - http://www.l3jane.net/doc//4600/index.htm

Older ones - scroll down to Post#22 - http://www.msfn.org/board/topic/171693-windows-98-se-in-depth-questions/ The Alienware one is older that the A406, BTW, and is the "full" package. HTH

Hmmm... it -appears- that SETUPX.DLL is responsible for the DRVIDX.BIN and DRVDATA.BIN. Also see this - "HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\SetupX\INF\OEM Name"

Would you kindly give the EXACT procedure for Install? I'm getting confused as you -seemingly- are randomly changing the method and files/folders in an attempt to make it "work". WHAT do you mean "crash"? "Like what you have"? What does that mean? Please provide your MSBATCH.INF (x-out the Product Key) and several INF files, along with the corresponding DIR listing for the "several" INF's (including the sub-dirs) mainly the "failing" ones. ZIP (or whatever) them first and attach the ZIP file to your next post. You are DEFINITELY doing something wrong! Again, I've used this method many times.

? So, why use the NUSB if the Drivers are on the CD? BTW, you DID read the "!README.TXT" inside NUSB, didn't you? Curious - did you install any Unofficial Update Packs? Did you install KernelEX?

Centipede car? Anyone think "Mars Rover"? http://en.wikipedia.org/wiki/Mars_rover

INFPREP.EXE? Is that one of your "creations"? Sorry, but I don't know what that is... Is that a "renamed" INFINST.EXE? I thought I made it clear what the "rules" are about manually altering the INF files to correctly install on FIRST REBOOT? Realtek AC97 is kind of "generic" isn't it? It IS "just" the INF + related modules, right? (I happen to have that EXACT file). From here - http://218.210.127.131/downloads/downloadsView.aspx?Langid=1&PNid=23&PFid=23&Level=4&Conn=3&DownTypeID=3&GetDown=false Here's WDM_A405 and WDM_A406, but they are EXE files that will need "unpacked" (WinRAR, WinZIP, 7Zip, whatever) - ftp://files.3dnews.ru/pub/drivers/SOUND/realtek/ edit - Also scroll down - this APPEARS to be the FULL "older" package (Rack App and all) - http://www.msfn.org/board/topic/171723-trouble-with-foxconn-661-7mj-motherboard/ ...and google this realtek "5.10.0"for more "potential" FULL packages. HTH

XP and DEP? http://support.microsoft.com/kb/875352 XP and UAC? From what I've "found", that's as much as using a "limited user account". Also (haven't tried this) but is this the concept? http://www.dedoimedo.com/computers/surun.html More info (ASLR is strictly Vista and up) - http://www.microsoft.com/security/sir/strategy/default.aspx?_escaped_fragment_=section_3_3#!section_3_3 So may I be confused by the article linked by jaclaz, or did I miss something?

This one MAY be your driver (it has the string in it) for the Realtek/ALC. Only thing missing is the "REV" part. http://www.downloadwindowsdrivers.info/pci/ven_1039/dev_7012/subsys_0c95105b/ Scroll down to the Alienware link for "m7700a_Audio_5.10.00.5930.zip". It's 30mb, but that's because it's kind of an AIO-type but the download is rather fast. The INF to install is ALCWDM12.INF. It also has the AudioRack software. Worth a shot and HTH... edit - DOH! The direct link is there (from copy/paste, I guess).

Ummm... do you have a CR/LF (press <enter>) after that line? There IS a reason that they are there between each Section of MSBATCH.INF. Also note the ";" delimiter between each path. Again, my sample works flawlessly, as well as the instructions for editing the INF files. USE <ENTER> (CR/LF) BEFORE EACH NEXT "SECTION"! HTH