Alanoll

screenshots help when I have no idea what you're talking about ERROR CODE 5 is typically cause by bad hexing. It matters if you use CAPITAL letters or not. Not in the file names, but when hexing. Be sure you're also hexing SETUPLDR.BIN correctly as well...

You do have the latest XPCREATE right? Maybe it's just me, but the one that does the incorporation of it, is distributed as XPCREATE.EXE no .ZIP

first..... http://www.msfn.org/board/index.php?showtopic=21582 second... THe problem has NOTHING to do with CDSHELL, but rather you editing of your DAT files, and SETUPLDR.BIN Recreate them, and be sure that the folder names are correct, and that you use CAPITOL LETTERS WHEN HEXING

not since you elminated DllCache via those Winnt.sif settings you have. it could be an error with the theme file itself. If there is one entry wrong, it won't load. Also, why don't you just replace uxtheme.dll on the XPCD in I386? Eliminates the possibility of having wrong file. Also, SFCDisable does NOT WORK. Might as well remove it, as it is replaced during Setup and First Logon, and Every Logon there after with the default value.

it's by Tobe

well, what language are we talking about? C++/C#/VB/VB#/Java/Perl/PHP/SQL/HTML/CSS/JAVASCRIPT/Pascal lol. Batch files aren't real programming. It's more BASIC then anything..... but if it helps, consider using a calender type thing, every time you add something, mark off the number. lol.

oh hey, I didn't know you actually wanted us to send stuff yet. I just signed up, cause you said to

well, I'm just saying... there's already a guide for multiboot... as well as slipstreaming.... Multiboot, granted there can be different ways....but slipstreaming? How many different possible ways are there? I'd be interested in seeing your guides nonthe less, as atleast the multiboot might have something Flyakite's mght not....

Changed.... I'm hoping to have time later this week/weekend to revamp the whole thing, and try to knock out as many of those little "known issues" as possible.

atleast you got to see it I could never get it.

please do a search. There is a line in winnt.sif that disables the Repair option. You may want to do an "multiboot" but not a true multiboot. Just one with two boot folders, one with winnt.sif one without so you get the repair option.

mask, is meant to be like *.* for all files, or *.dat for all dat files.

ditto

you're supposed to drop it into your Win98/ME boot disc image. I wrote that btw. You should have also used QUOTE tags. It looks better, and shows you're quoting. And actually there are examples of how to use it. set CDROM=FOO23 FINDCD.EXE if "%CDROM%"=="FOO23" goto QUIT That's how you use it. The IF EXIST lines, could cause problems with ZIP drives or the like if you don't have a disc in the drive.

you may find this article interesting.... http://www.cnn.com/2004/TECH/internet/07/0...reut/index.html

what is the point of having yet another guide? Im just curious. And another guide for slipstreaming....which isn't all that neccesary... -s:(PATH) and you're done.

Mozilla may require a search through the Application Switches forum.....

also, most people don't try to bypass the "SVCPACK limitation" but using CMDLINES.TXT, as they recognize it's essentially the same part of setup. Though you read the first sentence, you did miss the second, which would be the reason most people don't try CMDLINES.TXT. and to clearify, you CAN install the DX9 patch, if you also use that little file Tobe made prior to running it, but AFTER you install DX9.

XPInstall supported ONE hidewindow i believe, but no "nowait". XPlode is the current incarnation of XPInstall. I've never noticed any slowness on my end, but then again....I never really time it all that often, as I leave after putting in the disc. also, you have the syntax for hidewindow correct, however, hidewindow only hides windows specified if they are running when XPlode/XPInstall are started. XPlode has the argument hide, which might do what you want.

you may consider just running the batch file, in your current setup. As long as the files aren't in the correct place (where they would be in a normal install) you'll just get File Not Found errors if any, when RunOnceEX actually runs, or you could just delete the keys in the before you even restart.

they're actually only neccesary because of the way Windows setup locates the files. Its all because of TXTSETUP.SIF..... In there, there is a section called [sourceDiskNames] that declares the ident files, and where to look for them. Think of them, as just a way of naming the disc, and making sure yo have the right disc.

dunno why it would hang if you didn't change anythign in RunOnceEX.cmd.... but what alot of people misunderstand..... The CMD file runs at T-12 (where you are freezing), but the actual RunOnceEX window that executes and installs everything runs upon restart. If there is a single syntax error, it might prompt you with something, and you have to press a key, but you can't as you have the window hidden. I still suspect you may have changed SOMETHING in the file, or any file you run from CMDLINES.TXT and that's causing the problem. You may not remember changing something, but just like....wrong switch here, type of thing.....or something.

%CUSTOMVALUE%, I meant what's defined in the [sTRINGS] section of a normal INF. You CAN'T do that with the hive files, as there is no real interpreter at that point. Everything has to be spelled out like it's stupid.

I deleted your other thread. No need for both.

the only difference between normal INF files and hive INF files, is that the hive ones don't like shorthand typing. YOu have to spell out everything, otherwise EVERYTHING APPLIES. You also can't use STRINGS (%CUSTOMVALUE%). also, I would suggest 0x00010001 as opposed to 0x00010003. ALso, in either case.....the value if it is a dword, needs to be in hex. COMPLETE hex, not short. 0x000005DC