pedro80

I found that the problem originated from me editing presetup.cmd So the problem was fixed, but I still wonder where this batch script gets called from..

I just did an install without Driverpacks.net now, and the command prompt didn't show up. The problem then originates from Driverpacks.net.. I will continue too investigate, If anyone cares to help me in regards to where things get executed from, please do

As I already stated, I have no 'DetachedProgram' entry in my winnt.sif.. Thx for the quick reply though

Hi guys! Probably a small problem for you gurus in this forum (please share your knowledge with me); I have this problem where a command prompt pops up at T39, before "installing devices". It doesn't halt the installation, but it's anoying and shouldn't be there I'm using HFSLIP and Driverpacks.net (these are the only two I reckon could cause this). Where do I look to figure out what is called at this stage? one of the SIF files? The unattended guide states "DetachedProgram executes from winnt.sif at T-39 stage", but I have no such entry in my winnt.sif..

Microsoft Security Bulletin Summary for February 2008

1: Go into your CDSHELL folder (named BOOT in my setup) find the subfolder "graphics" and delete the "splash.csi" file. All done. Alternatively you can make your own splash screen, brief description here. 2: In my AIO setup only the PRO1, PRO2 etc. folders (and sub dirs/files) in root have caps. Don't remember right now but think maybe my cdshell folder also uses caps. The rest of the DVD isn't using caps. My setup is fairly similar to this.

You may also want to have try Autopatcher for updating systems already installed..

Yeah... he needed a break, he's been poundin' since I registered

@Black Wolf: Thx @sven: You say "to send Firefox traffic down VPN tunnel"; Any chance you could explain briefly how you do this? I'm having serious issues with the webwasher-feature installed in the proxy at work. I would like to be able to relay all my traffic through my home server..

You are using DriverPacks.net? Are you using the newest BASE? 7.0.0.11 (or something like that.. driverpacks.net is unavailable at my current ISP@work). In that case, there's a known bug in this release causing the textmode integration to be skipped. The team is working on it and there is already a beta of 7.0.0.2 in the developer-team. ETA was a couple of days it was said in the driverpacks forum.

Firefox Portable with the following extensions (sorted in preferred order:): Scrollbar Anywhere - http://perso.orange.fr/marc.boullet/ext/extensions-en.html (right click to scroll anywhere on the page) Foxmarks (bookmark sync.) - http://www.foxmarks.com/ (sync. all your bookmarks between different PC's) Adblock Plus - http://adblockplus.org/en/ (need to block those AD's) Filterset.G Updater - http://www.pierceive.com/ (don't want to create AD-block list myself) MinimizeToTray - http://minimizetotray.mozdev.org/ (keep FF running in the tray) Gmail Notifier - http://www.nexgenmedia.net/extensions/ (get notified on new mails) IEtab - http://ietab.mozdev.org/ (IE is owned by, and ran, inside FF. For incompatible web-pages) Tabbrowser Preferences - http://216.55.161.203/theonekea/tabprefs/ (extend FF settings for tab browsing) Download Manager Tweak - http://dmextension.mozdev.org/ (tweak the "downloads"-window and put it as a tab) Linkification - http://yellow5.us/firefox/linkification/ (non <A>-urls in webpages made links) Restart Firefox - http://jedbrown.net/1.0/mozilla/extensions/ (restart FF in "file"-menu) DownThemAll - http://www.downthemall.net/ (download manager to do batch downloading)

Seems the only thing left is to try a different PSU and a different CPU. (off course keep the server stripped, i.e. no hdd, fdd, cdrom, extra controllers etc.) If one of these two options doesn't work, the motherboard is probably dead..

I'm bumping this in hope of update of download mirrors, or maybe somone else would care to upload these files elsewhere if they have already downloaded them..

About the large icons: I'm not sure of this, but since you havn't gotten any answer I'll might as well try to help you. Refering to this post, look at the first reply. They refere to a registry string which has to do with Theme-manager. Maybe if you set your computer to use large icons, there will be an regentry about the icons in that location in reistry.. Altarnate you could use one of those monitor-your-registry-entries-programs (don't remember any names right now). Such programs monitor any changes done to your registry. Try to start such a program, enable large icons then stop the program. Then you'll be able to see what reg-key has been changed.. Good luck

Yes, figured it out.. I just didn't see any reply from you confirming that this actually fixed your problem

Any update on this issue? I'm having the same problem..

Great It was as I suspected then.. I could only find that your packs were made for WinXp, but then I saw that post where you implemented the tag check for KB888111, so I wasn't sure.. Anyways, I can report that elswhise it works seemlessly with BASE, CPU, Chipset, mass-storage and LAN vs. Win2k3 Sp1 I'm going to run som tests on different hw the next days, so I'll report in if theres any more compatibility issues

Hello! I ran into your slipstreamer couple days ago, and I got to hand it to you: great work Nevertheless, I think I may have discovered a flaw (not sure if it is or if you deliberately did this). I'm slipstreaming W2k3 Sp1 with all post Sp1 fixes. What I discovered is this: after "merging" the sp1.cab into driver.cab, the script modifies DRVINDEX.INF and TXTSETUP.SIF. The problem is that in my W2k3 folder I have a DOSNET.INF file which also has references to Sp1.cab.. This generates an error during installation reminding me that Sp1.cab can't be found. I've been able to fix this by manually editing the DOSNET.INF file, just removing the line which refers to Sp1.cab. I'm not sure if my case is a special case or if DOSNET.INF normally resides in the W2k3 installation path (as I'm not very experienced in these slipstreaming processes) My suggestion (if fix is needed), insert this in the CABCOMPACT-section, before line 2044: IF EXIST SOURCESS\I386\DOSNET.INF ( ECHO Updating DOSNET.INF FINDSTR /V /I "SP1.CAB SP2.CAB SP3.CAB SP4.CAB SP5.CAB" SOURCESS\I386\DOSNET.INF >WORK\DOSNET.INF DEL /F /Q SOURCESS\I386\DOSNET.INF XCOPY WORK\DOSNET.INF SOURCESS\I386 ) attached my ERROR_REPORT.TXT for reference (don't think it'll help in this matter though), keep up the good work ERROR_REPORT.TXT

I'm having a possible problem here.. Using the latest releases (according to UpdateChecker). Trying to slipstream CPU, Chipset, mass-storage and LAN to a fresh Win2k3 (/w sp1 slipstreamed), having two problems: 1. I see that you implemented a fix to ensure that if wink2k3 don't slipstream KB888111, fair enough. But earlier in the process you have a section called REM ### If KB888111 is slipstreamed, it will be deleted, UNLESS RyanVM's UpdatePack is detected!. ### This one deletes files in my Win2k3 I386-directory needed for propper installation of Win2k3.Sp1. The result is windows-installation informing me that it cannot copy some eight files.. 2. For some reason I can't figure out Sp1.cab is missing after slipstreaming the drivers.. I've looked through your code, but can't figure out why this happens.. Thanks for the enormous amount out time you spend on this project, I'm all greatfull Edit: Forget #2, some other error whilst using HFSLIP Edit#2: I've now confirmed this by REM'ing out the lines intended for deletion of the KB888111-files. One suggestion to correct this could be to move the deleting-code to run after REM ### If any of Windows Server 2003's tagfiles are detected, KB888111 will NOT get slipstreamed. ###

Apologies.. It's us that should apolgize for even annoying you with this.. Thanx a lot for supplying these packs and your slipstreaming batch-files, you sure are a great guy

Shouldn't Bashrat first approve of such an action..?

Mee too.. Seems too many has Dl'ed today Edit: Any chance someone could be allowed to set up a temporary mirror?

Yes please do These guy's are not alone on this problem.. Regarding other things to be fixed: (just to mention them, seems like you're allready aware of them. And as I can see from your posts, they will be fixed) -After slipstream, M2, I always have to replace cmdlines.txt with my original. -After slipstream, M2, I have to add "DriverSigningPolicy=Ignore" and "NonDriverSigningPolicy=Ignore" to my winnt. sif. -Tried to use M3, but no drivers extracted. Even tried to delete the cleanup-batch to be sure. *Note, this is not to nag Great system you have going here with the DP's