VCC

This has been an annoying problem for a while. Check out the Driverpacks, the latest version uses a utility to get around that mess.

Appears that I misunderstood. BUT, (and I could be mistaken, I'd ask Siginet because he'd be the best source to verify) the RVM Integrator is setup to integrate pretty much anything one way or another.

Well there is the RVM Integrator, though, RyanVM has been busy. So, Windows updates have been on hold lately. Check out siginetsoftware.com I know siginet has an Office update integrator for 2003.

Have you read the Unattended Guide? Check out the Driverpacks solution in my signature, works great for most, if not all, Dells. Might be more than you need, but will provide the best solution in the long run. Also, check out the RVM Integrator and Siginet's Powerpacker. That should be enough for now. Time spent will not be in vain.

Are these PCs from manufactures like HP, Dell, etc.? Or are they PCs you are building (Clones)? Because if they are by HP, Dell, etc. just find and use the royalty keys (they can be extracted by an original build using OEMGetFiles utility) and check out this project: http://siginetsoftware.com/forum/showthread.php?t=117 This way, Windows is activated with the key it originally came with and you and the client don't have to worry about other OEM keys. It is legal, because you are getting the PC back to the way it was.

Did you come across this in your search... http://www.msfn.org/board/lofiversion/index.php/t21270.html You might be missing this registry entry or make sure you are setting the Control Panel to classic as well. I'll leave the testing to you, I have no desire to have a classic menu at build time. Just wanted to be of some help. Good luck. [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer]"NoSimpleStartMenu"=dword:00000000 For Classic Control Panel: [HKEY_Current_User\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer] "ForceClassicControlPanel"=dword:00000001 Since I noticed you didn't have it included. Also, check out the following site, it has some additional info: http://windowsxp.mvps.org/nosimplestartmenu.htm

Well, in case you're not aware. DSPDsblr.exe is "Driver Signing Policy Disabler" which is part of the Driverpacks, I think it is a function of the Finisher portion of it. So, if you are able to get to where the setup is running there may be a problem with the Driverpack setup. Seems the DSPDsblr.exe is not copying over. It runs when setup installs drivers so you're not getting a bunch of errors. I know, this may not be a lot of help, but I thought I'd pass it on anyway. Make sure you're pointing correctly to your source and you're choosing disk for the platform. Otherwise, you might want to try posting your problem in the Driverpacks forum. You'll probably get better help there since those who work with that project are going to be concentrating there for these kind of posts.

Seriously. For those custom cursors to work you will probably need the latest version of a - must/dare I say - hacked uxtheme.dll file. Though, in this forum I don't believe I can help point you in the right direction of one. Might be against rules. So, with that said, you'll probably be able to do some searching and find a topic somewhere on that.

Get to know the Ryan Integrator and Siginet's Powerpacker utility. These will help with both of your needs. The integrator will help if you also want to integrate Windows updates, integrating applications. The Powerpacker will help with making an XP CD that is not only bootable, but that can be Multi-purpose. You can also use the Driverpacks if you have different models of Optiplexes because I know from experience that the driverpacks have a lot of Dell drivers in them. All the links you need are in my signature. Have fun and Good Luck, if you get to using these utilities you will not be waisting time or regret it.

Yeah Dude, Driverpacks are Awesome!!! Click in my signature

I'd like to be the first to say that it sounds like you're on to something here. I am normally pretty good at guessing what is good and not good to be in startup\Registry Runs, etc and what I don't know I research with google. But a program like this would be nice. I'll be interested to see what you're able to come up with. I'll surely help by passing stuff along to you as I come along them.

You might also try Bashrat's Driverpacks. He's been perfecting those for years now and has a proven method already, instead of trying to go at it on your own. Works awesome for Sysprep too, I use them all the time without problems.

You're welcome. Glad I can spill some new settings your way. The only thing that raises a question to me at the moment, the brain is a bit tired at the moment and I'll have to look at this again tomorrow when I'm fresh, is the [userData] being toward the bottom of the file. I thought I read somewhere about the positioning of the sections. I don't know if you've tried this already, but it might be worth a try to reposition it a bit. I'm also catching that you do not have an OrgName listed. Try including that, even if it is blank, I think setup wants to see something there. You can just put OrgName="" for a blank setting. If I see something else later I'll pass it your way. I know it can be frustrating when this stuff doesn't work. Hope you find the answer soon. For settings in my sif I pretty much searched in many different sif files and checked Microsoft's site and different forums for what they were used for. Also trial and error.

zakum, there is no space in his example. It may look like it due to the CODE window though. toffo, maybe you can list the rest of your winnt.sif or unattend.txt file so we can get a better idea of what you're dealing with. What you have already, in your post, should be working in my experience. Here is an example of mine and it works fine: ;SetupMgrTag [Data] AutoPartition=1 MsDosInitiated="0" UnattendedInstall="Yes" [Unattended] AutoActivate=No CrashDumpSetting=3 DisableVirtualOemDevices = Yes DriverSigningPolicy="Ignore" DUDisable = No UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=Yes OemPnPDriversPath= Repartition=Yes TargetPath=\WINDOWS FileSystem=ConvertNTFS UnattendSwitch=yes WaitForReboot=no NtUpgrade=No Hibernation=No [Backup] EnableBackup=No [GuiUnattended] AdminPassword=password EncryptedAdminPassword=NO AutoLogon=Yes AutoLogonCount=2 OEMSkipRegional=1 OemSkipWelcome=1 TimeZone=4 [UserData] ProductKey="xxxxx-xxxxx-xxxxx-xxxxx-xxxxx" FullName="Default" OrgName="Oganization" ComputerName="personal" [Display] BitsPerPel=24 Xresolution=800 YResolution=600 [TapiLocation] CountryCode=1 Dialing=Tone AreaCode=805 [RegionalSettings] LanguageGroup=1 SystemLocale=00000409 UserLocale=00000409 InputLocale=0409:00000409 [Identification] Joinworkgroup = workgroup [Networking] InstallDefaultComponents=Yes [Proxy] Proxy_Enable=0 Use_Same_Proxy=1 [Components] dialer=on freecell=on hearts=on minesweeper=on pinball=on solitaire=on spider=on zonegames=on msmsgs=off msnexplr=off media_clips=on OEAccess=off [Branding] BrandIEUsingUnattended=Yes [URL] Home_Page=http://website Quick_Link1_name="website" Quick_Link1=http://website [FavoritesEx] Title1=website.url URL1=http://website You'll want to focus on the [Data] and [unattended] sections.

Check out PowerPacker, it will do it for you. The link is in my Signature...

Are you using the DriverPacks? Maybe you'll want to consider this. I'm suprised no one else mentioned this. Check out my signature for location of these. Together with the PowerPacker, it may help. It's really easy to add unsupported drivers in the DriverPacks too.

The one major difference I see, besides the order, is that you have quotes around the password and I don't. Try removing the quotes and see what happens.

The answer to what is slipstreaming, in relation to integrating, is at the end of the first paragraph here: http://hfslip.org The difference is that slipstreaming places the updates or hotfixes on the installation source and runs them during install of the operating system (which can take several minutes every time you want to install an operating system, not an efficient use of time). Where Integration (which I have found is a much better and quicker way of operating) actually takes those updates/hotfixes and uses them to replace the original installation source files and you end up with an installation that is up-to-date. RVM Integrator helps you with this, it integrates those updates, essentially updating your installation source and it is so easy that even a 5 yr. old can do it. Well, maybe. I haven't proven that yet. B)

Your answer should lie within Windows Explorer. For instance, open Windows Explorer by either opening My Computer, or right-click My Computer and select Explorer. Now select List View from the View menu, then Go to the Tools menu and select Options. Select the View tab and click on "Apply to All Folders" (Click Yes on the Folder Views window that will popup, it may also be a good idea to scroll down the list in Advanced Settings and make sure that "Remember each folder's view settings" is checked. Hopefully I understood your problem and this will help you.

I normally get this type of error when the cd/dvd drive is not working properly. I have changed out drives and found it to be the drive. Or it could be your cd/dvd media. You might try creating another disk. I've been there, it is frustrating. Especially when you don't have another drive to swap out to test whether it is the drive or another computer to try your disk in. Good luck, hope this info helps.

You should have posted this in Site & Forum Issues I believe. Same problem here.

I don't presume to have an answer. Though, I do have a thought. I went through a similar situation and found it was the BIOS that didn't fully support the memory I had. Luckily they had produced an updated BIOS which happened to fix the particular problem and supportted more memory. Now the server is running, almost, great. I say almost because I now have a couple of, what seem to be Active Directory problems. When the client goes to login it takes a minute to get to the desktop (Microsoft apparently has a hotfix I need to get) and when trying to add a group to the Administrators group on the PC it will not find the domain (even though the group does have Domain Admins in it and that works) Good luck, I hope your issue gets solved quickly. As I know the frustration it can cause. 3 trips back to Fry's Electronics to replace the memory and the problem got solved. I should have known better than to update the BIOS first.

Yeah, the best way I've found is the RyanVM Integrator. Check out the link in my signature.

Actually, for a forced install I believe you want, forc[pn]=['no']; to be: forc[pn]=['yes'] Also, your switch is to close to the executable. cmd1[pn]=['%wpipath%\\Install\\Sonic.DVDit!.v5.RETAIL-CROSS.30-7-04\\Setup\\setup.exe/VERYSILENT ']; should be: cmd1[pn]=['%wpipath%\\Install\\Sonic.DVDit!.v5.RETAIL-CROSS.30-7-04\\Setup\\setup.exe /VERYSILENT ']; Notice the space between setup.exe & /VERYSILENT otherwise you command is seen as setup.exe/VERYSILENT and the O.S. will not find that.

Well, unless someone else has a better idea, I would say, "Yes, try it without that setting." Although, it does sound like a helpful setting otherwise. Another suggestion would be (just for troubleshooting) to try kicking down the BitsPerPel=32 to 24 rather than 32. Or remove the Vrefresh=60, maybe try a lower setting there, maybe 70 or 75. You could be pushing it to hard in the beginning. I know that's the idea, but something is not liking that idea much.