LeveL

Get "Startup Control Panel" by Mike Lin. Its free, tiny and its just a standalone exe... http://www.mlin.net/StartupCPL.shtml

It happens using Bashrat The Sneaky's Driverpacks when you try to do a repair installation. You must have removed the OemPreinstall=Yes from the WINNT.SIF file or something. You need to at least have these sections and commands in I386\WINNT.SIF The vicious circle is - if you have an [unattended] section there, you will lose the ability to do a repair install.

What is the BSOD? RDR_FILE_SYSTEM? If it is then its because of Event Log. Sounds silly but when stripping Server 2003 out, I had to disable Event Log during install then on second to last reboot, re-enable Event Log. I am not saying try this, but it was a wierd problem I had. I never noticed nLite showing services that arn't there. Mount Manager... thats a sys file mountmgr.sys thats related to System Restore, which is not even in Server 2003. I dunno where you were looking but nLite does not show any services under "Services" that are not in your services.msc window when you look in the installed OS, well OK the Beep Driver and POP3 services... but theres no Mount Manager there, see:

One hour? I was going to say check if your hard disk is set on some ridiculously low transfer mode like "PIO Mode" but even that wouldn't take an hour.

The only flaming I will do is... its not "eeeso" its I.S.O.

Now Server 2003 SP2 is finally released, I would like to include it in my multi-boot DVD as opposed to the now dated SP1 version. One problem, the same thing that is always the problem - setupldr.bin Anyone remember all the trouble with SP1 when that came out, you couldn't just replace the text "I386" with your own folder name like "ENT1" because it gave you the error: "NTLDR is corrupt". The answer was to either use the setupldr.bin from SP0 or call your folder something crazy like "83i6" or "i683". Then geitonaki found the answer here: http://www.msfn.org/board/index.php?showtopic=58410&st=0 But this hex editing trick does not work on the SP2 version of setupldr.bin I tried using the hacked SP1 version of setupldr.bin on SP2, it does not work. I tried using the SP0 version of setupldr.bin on SP2, it does not work. So we are back to square one again if you want to use Server 2003 SP2 in a multi-boot. I think what we really need is some tool to crack, not hack but crack the setupldr.bin so it has the same CRC number even though you have changed the file, of course only people like James Bond have such tools, although that would fix it. All I keep getting is either: "NTLDR is corrupt" or... "NTDETECT Failed"

Yes LeveL, no LeveL, glad to answer you in 5 months LeveL. This is exactly why I am posting here again... 1 - I got the (original, from my own CD) setupldr.bin file from Server 2003 SP2. 2 - I opened the file in Hex Workshop and at the address 00002060 I hex edited the value "7403" so it said "EB1A" 3 - I got the message "NTDETECT Failed" Since the flyakite guide went down, I am not totally sure I have done it all properly because I had to do the whole thing off memory but yes, I deleted BOOTSECT.DAT and migrate.inf from the boot folder. Whats really annoying me is I made my Server 2003 SP1 multi boot somehow! Because - it is made, but now SP2 is here I am trying to make one for SP2, and I have posted above in November 2006 asking this exact same question but lol, I KNOW I DID FIX IT because I have made a working Server 2003 SP1 multi-boot. No - the SP1 version of the setupldr.bin won't work, its the 1st thing I tried. Maybe we need a fresh DAT file for the root of the DVD? Where the hell does that DAT file come from anyway? I mean the one that has one single reference to I386 at the very end of it and you change it to your boot folder name... I only ever got that DAT file from flyakite in the past. Please, can anyone test Server 2003 SP2 and do the thing mentioned in the first post to change the hex values? I just need to know its me thats done something wrong and we're not going to go through all this crap again because its now SP2

Thanks for mirroring the original guide but what I need is the original command you paste in the Start > Run box to obtain the boot files, because I am using Server 2003 not XP and this guide only covers XP with an automated SFX to get the boot files. Anyone know the command?! I know its something to do with: winnt32.exe /noreboot but I can't remember it! DOH! Thats literally all it is: D:\I386\WINNT32.EXE /noreboot Don't do a dynamic update, click advanced and tick to copy all files from the CD, then when its done that, grab the files from C:\$WIN_NT$.~BT Then whatever you do, make sure to take the lines out of C:\boot.ini Sorry if you read this, you didn't need to

Dunno if this will work but I am listing the files in TXTSETUP.SIF This is just two sections of one file! I guess DOSNET.INF and others might list driver files.

At the moment I am trying to unpack a folder to the C:\ drive that will contain the driver files and INF files. I am doing this from cmdlines so I think it might be too late. When Windows says "Setup is installing devices such as your keyboard and mouse" I am sure thats when other stuff like Printers, Scanners, Modems, Sound Cards get their drivers installed, if thats the case then cmdlines runs AFTER this so it won't work but I am testing it now. I will try your way above if my way doesn't work out... if that doesn't work I will have to unpack and just have the 50Mb worth of drivers there (actually its 55Mb with the INF files) and try to strip a few things from the install but I really didn't want to strip the OS. EDIT: Well I ended up removing a few things with nLite, that has freed up 50Mb of space, the drivers are all expanded now and I am trying the OemPnPDriversPath method. --------------------------------------------------------------------------------------------------------- AAAAAAAAAGH! It has not installed the sound drivers! I suppose I will have to try the hard way packing them into DRIVER.CAB and listing them all in TXTSETUP.SIF.

Wow - this seems like a very quick and easy fix, thanks... but my main problem is that I don't have the 50Mb spare needed to store these driver files. I guess if I strip out the UDDI service (33Mb) and a few other things, like Printer drivers (another 33Mb) I can fit all these files on the CD. So I should search the XP I386 folder for ".IN_" and use whatever *.IN_ files are not on Server 2003? OK, I think I understand this, those IN_ files need to be uncabbed and PUT WITH the driver files... it seems to be quite straightforward. Yeah the [sCSI.Load] section etc - but why are all these driver files (from inside DRIVER.CAB) all listed in TXTSETUP.SIF? I have slipstreamed some Bashrat drivers, my WINNT.SIF is like this: You said do it so these lines are there: So the only difference is that this is added: -------------------------------------------------------------------------------- Well OK what about this: When does this OemPnPDriversPath get read? I mean, is it possible to add all these drivers and INF files to a 7z archive and unpack it to "%SYSTEMDRIVE%\Drivers\Plus" at the cmdlines.txt part of setup, will it be "unpacked in time" for the OemPnPDriversPath to install the drivers? If that could be done (and this is getting almost like what Bashrats driverpacks do) then it would be excellent because those 50Mb of drivers could be 7zipped down to only 8.90Mb

As a famous prophet once said: "F**K THIS FOR A GAME OF SOLDIERS" I wonder if theres some way to slipstream these drivers with BTS, HFSLIP or nLite? How are any of those programs going to know the comma's and numbers its supposed to have? For example: That is just the first 13 files out of 351 files. Some files appear under multiple sections: [sourceDisksFiles] [sourceDisksFiles.x86] [Files.DeleteOnUpgrade] [HardwareIdsDatabase] [sCSI.Load] And MANY MANY more! --------------------------------------------------------------------------------------------------- You know it would actually probably be quicker to hand code a program all of its own that searches TXTSETUP.SIF for these lines, adds them to a new TXT file under the correct sections and so on. 351 files, its too much work to do by hand.

So you mean... all those *.IN_ files in XP have drivers listed? I am looking in TXTSETUP.SIF and it has listed every file that is in DRIVER.CAB. So I will have to do this: 1 - Open the folder with the 351 added files (those are in the DRIVER.CAB for XP but not in Server 2003) 2 - Open a new notepad TXT file and call it "OMFG I can't believe I am doing this.txt" 3 - Copy the name of the first of the 351 files. 4 - Open my XP TXTSETUP.SIF file and Ctrl+F for that file. 5 - Once I find it, copy the whole line it is on and add it to the new text file, of course also noting the [sections] it appears in as I do it. This is an INCREDIBLE amount of work. I could always work on one letter a day and it will take about a month to do it and even then, its not guaranteed to work, or is it? You said the files are also listed in INF files! This is a nightmare, why can't JERKOFF MICROSOFT just put the drivers in there in the first place?!

Thanks, but I want to add ALL the drivers from XP into it, somehow. Well everything I said in post #3 has not worked. I guess the drivers in the CAB file are listed somewhere huh. Time to start f**king about adding 351 lines of code to some f**king INF file somewhere. OMFG the files ARE listed, in TXTSETUP.SIF under [sourceDisksFiles] So yeah, now I have got to add the 350 lines of code to that... Microsoft, why do you make it so difficult?

Thanks... I have tried something else, I have got to test it yet though: 1 - Extracted DRIVER.CAB from Windows XP into a folder "XP\DRIVER" 2 - Extracted DRIVER.CAB from Windows Server 2003 into a folder "2003\DRIVER" 3 - Opened both folders side by side. 4 - Scrolled to the bottom of the "2003\DRIVER" folder. 5 - Copied all the files from the "XP\DRIVER" folder into the "2003\DRIVER" folder, overwriting nothing. 6 - Copied all the added files from the bottom of the "2003\DRIVER" into another folder. This turns out to be 351 files! DRIVER.CAB on Server 2003 as standard = 55.4Mb DRIVER.CAB on XP as standard = 60.4Mb When I recabbed the "hybrid" drivers (2003 with added XP drivers) with Power Archiver - my DRIVER.CAB is now 80.0Mb. So there are a lot of drivers in XP that are not in 2003 - and vice versa! I will just have to test it to see, because what i said before about those drivers all being listed... they are not listed anywhere as far as I know, it would be nice if Windows just dealt with the device installations seperately and managed to use "whatever" drivers are in DRIVER.CAB. Its not just sound drivers - the following drivers are also included with XP that are not in Server 2003: Adaptec SCSI Miniport AdvanSys SCSI Card Driver Compaq Drivers (tons of those!) Creative SB Live! Adapter Driver Creative SB Live! Interface Driver ESS Technology Audio Driver Hewlett-Packard ScanJet 2100C/3300C/4200 Device Driver Modem Drivers (tons of!) U.S. Robotics That is just a fraction of whats added in the "hybrid" DRIVER.CAB!

On Microsoft's own website on a page about troubleshooting the audio in Server 2003 it says: A sound driver may not be installed. Windows Server 2003 includes a limited list of sound drivers. Yes it does, because with XP in VMware, the sound driver is fine, it installs, but with Server 2003 it does not work, where Microsoft say "Windows Server 2003 includes a limited list of sound drivers" I think they mean it is VERY limited. Is there any way to add the drivers for sound that are in XP to Server 2003? Where would I start? I know you can't just throw them into DRIVER.CAB because those files are all listed in INF files so if the XP sound drivers were inside the Server 2003 DRIVER.CAB, it wouldn't make any difference! Or so thats how I understand it, to be honest I really don't understand it, thats why I am asking! I know I could just use Bashrat The Sneaky driverpacks but the sound drivers alone are 100Mb... far far too big! I only want to add the core sound drivers that are obviously in XP (because they work in VMware) but not in Server 2003. Strange thing is, on my real system the sound drivers do install for my onboard sound, but its VMware where I want them working. I installed the Creative sound driver in VMware and it added these files to C:\WINDOWS\system32\drivers\ ---> As you can see from the descriptions, it is not totally obvious what are sound drivers and what arn't! They don't have sound driver-ish names. The real kicker is... none of these files, not a single one, even exists in the Windows XP source folder! Please tell me someone has made a simple add-on for these drivers?! Because DRIVER.CAB in Windows XP contains thousands and thousands of files, no way am I reading through 1000's of file descriptions!

I always used this tweak to enable "Cleartype" for the system font... [HKEY_USERS\.DEFAULT\Control Panel\Desktop] "FontSmoothing"="2" "FontSmoothingType"=dword:00000002 [HKEY_CURRENT_USER\Control Panel\Desktop] "FontSmoothing"="2" "FontSmoothingType"=dword:00000002 Its always worked until I slipstreamed the newly released Service Pack 2. I have tons of other tweaks and they are all working the same as they always have, but this one is not sticking for some reason. The above code says HKEY_USERS\.DEFAULT because I am applying it at the T-12 minute stage and also when Windows has installed just before the final reboot to try to make it work, but it just won't work, stuck with that horrible looking pixelated font still! Anyone else noticed this? I can enable Cleartype manually, hell I can even apply the registry tweak from a reg file and reboot and it works, just not whilst Windows is installing. Yes, when it applies it is logged in as the current user, my tweaks go in after the first time Windows logs into a custom user account, so I don't see why it being HKCU should affect it, unless for some reason it is because I am using both the .DEFAULT and the HKCU tweak and it is conflicting?

Thanks man, I don't need this info for doing this now but it is certainly gonna be useful in future I am sure.

I searched the registry for these terms... Format Form&at Format... Form&at... It does not appear in the registry. So I wonder if it is in hex values? Nope, because I already searched for the hex equivelant. Methinks nobody knows how to get rid of this I have been trying for almost 2 hours.

I don't want the "Format..." option on the right click of my disk drives, I have removed the "format.com" file but just need to get rid of the context menu item, anyone know of a tweak to remove it? I have searched Google and this forum, to no avail...

I have a similar problem, I stripped most stuff out with nLite, but then continued on "the hardcore way" and removed about another 200 or 300 files. Now I want to add back Logical Disk Manager! Its Server 2003. Its needed in Server 2003, othewise you'll never see your added hard disk in My Computer, whatever the disk is, IDE/SATA, anything... not sure if its any different in XP. I am trying to add back Logical Disk Manager. I have added back the 22 EXE and DLL files required for Logical Disk Manager and Computer Management, I have also added back each file to the TXTSETUP.SIF file too, I am not sure if thats going to be enough, only Nuhi knows the answer to that... I suspect there are INF files involved too? I wonder if this will work... 1 - Get a clean full OS, in a folder called "LDM-YES" 2 - Put that same OS in a folder called "LDM-NO" and strip out ONLY the Logical Disk Manager. 3 - Compare the 2. But then theres about 10 or so INF files that are editied by nLite, not removed! Thats where the trouble is going to lie, oh well there arn't that many uncabbed INF files on the root of the source.

I worked it out, I think. All the stuff in the first post doesn't apply, I removed this key and it removes the folder... Windows Registry Editor Version 5.00 [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel\NameSpace\{D6277990-4C6A-11CF-8D87-00AA0060F5BF}] ;

I have removed a lot of stuff from Server 2003, I am having problems deleting a registry entry that relates to a blank folder in Control Panel. The blank folders description says: "Schedule computer tasks to run automatically." I have removed Task Scheduler so I don't want this folder appearing here. If I search my registry for "Schedule computer tasks to run automatically" I can find the entry under this key: [HKEY_CURRENT_USER\Software\Microsoft\Windows\ShellNoRoam\MUICache] When I make a .REG file to delete it like this: It does not delete the entry. 1 - Yes I am logged in as Administrator. 2 - This is unattended, so I have tried doing this tweak at the T-12 minute stage from cmdlines.txt, both trying to remove the entry under "HKCU" and also "HKU\.DEFAULT" - it won't work. 3 - If I manually delete the entry it comes back again. 4 - I do not have any programs running that might be "protecting" the registry. 5 - I used Dependency Walker to see if the file REG.EXE depends on any other files, all the DLL files listed in Dependency Walker were put back in system32 and all the ones I could register were registered, it still does not remove the entry. 6 - I have tried referring to the entry as: "@C:\WINDOWS\system32\SHELL32.dll,-22923" AND "@C:\\WINDOWS\\system32\\SHELL32.dll,-22923" 7 - I tried it with a batch file like this: Doesn't work, batch files OR reg files, nothing is working! --------------------------------------------------------------------------------------------------------------------------------- Would it be possible to edit an INF file in the Windows setup so this entry is not created in the first place? Which INF file would it be? There are more than 150 .IN_ files in I386 ---------------------------------------------------------------------------------------------------------------------------------

Oh. My. Goodness. Its. Doing. It. Again. Flash Player is taking LONGER THAN WINDOWS to install! What causes this? I have already bypassed this stupid ten minute long install for Firefox and Opera by putting the DLL file "NPSWF32.dll" in both the plugin folders for those browsers but what about Internet Explorer? Where would the file "NPSWF32.dll" go if I wanted to do it as a plugin for Internet Explorer?

Very unlikely - I am almost 100% sure it won't work. If you're going to do that make sure you save a copy of TCPIP.SYS somewhere! Remember, Vista does not have TCPIP.SY_ in an I386 folder like all other previous versions of Windows - yet another of the hundreds or even thousands of reasons why I wouldn't go near Vista with a barge pole. INSTALL.WIM ?????????????? What the hell were Microsoft thinking? Why have they made Vista so all the files are locked away in a WIM image? They are complete TOOLS for doing that, how does locking all the files away in a WIM image help anyone? Just proves really that Microsoft are obviously not out to help people, I think the discerning among us can see that.