jrzycrim

Lol! I use a custom theme and I always hated the switch between the default and my settings during the logon process. I copied these keys and then imported them into the [HKEY_USERS\.Default...]: [HKEY_CURRENT_USER\Control Panel\Colors] [HKEY_CURRENT_USER\Control Panel\Desktop] [HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetrics] [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\ThemeManager] This will ensure that the theme settings you use are the same during logon. I figured just the one setting would be needed for the classic theme...

Try this: [HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\ThemeManager] "ThemeActive"="0" The settings found in this key as well as [HKEY_USERS\.DEFAULT\Control Panel] is what will be used at the Logon screen.

http://www.msfn.org/board/index.php?showtopic=19918&st=5

I would have guessed no considering the limitations of what you can do with detachedprograms. However, here's an interesting thread: http://www.msfn.org/board/index.php?showtopic=19838&st=0&

You can launch mplayer2 from the command line. There are no command line switches, however. start /min mplayer2 filename That would launch mplayer2 minimized. You could use pskill to end mplayer2 or just let windows kill it at reboot. You could even have it load an m3u playlist if you wanted more than one song. By the time RunOnceEx is going, sound drivers should already be in place as well as the codec necessary for mp3 playback. If you using a prepare.cmd file in RunOnceEx, I'd recommend placing the above command in that. Cheers,

Here's a possible workaround for your control panel tweak. I didn't have time to actually test this on an unattended CD. Just takes to long. I set the control panel to category view. Next, I imported the tweak I posted earlier: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer] "ForceClassicControlPanel"=dword:00000001 I then immediately deleted that value: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer] "ForceClassicControlPanel"=- When I opened the control panel, it was in classic view and the ability to switch to category view was not disabled. This might work during setup if you import the reg key from cmdlines.txt and then delete that key during RunOnceEx or GUIRunOnce. I can't be sure it will work, however. Cheers,

Check this out: http://www.tweakxp.com/tweak683.aspx The instructions there said 24x24 but the icon should be 32x32.

When your making a post, scroll down and you will see the browse button for attatchments. Do you have a custom shell32.dll?

I wouldn't think the uxtheme.dll would cause that. Maybe the actual theme you're using? I highly doubt that would be the problem but you never know... I've seen some pretty funky themes that did weird things.

AVG 6.0 Free edition

Try this instead: [COMMANDS] "useraccounts.cmd" "REGEDIT /S regtweaks.reg" "RunOnceEx.cmd" Beat me to it!

http://www.sysinternals.com/ntw2k/freeware/pskill.shtml

Check out this page: http://unattended.msfn.org/xp/applications/powertoys.htm You need to download the tweakui that was repackaged by Ytterbium. Also, all other powertoys support the /s /v/qn switch. Another thing you can do for your DirectX entry is change it to this: REG ADD %KEY%\010 /V 1 /D "\"%systemdrive%\install\DirectX 9.0b\DX9NTopk.exe\" /qn" /f That puts the entire pathname in quotes so that the spaces will parsed correctly.

1: Windows cannot find 'C:\install\DirectX'. In your RunOnceEx, Your path to the directX file has spaces. That's causing windows to ignore everything after the first space. It's trying to execute the file 'C:\install\DirectX'. I'd recommend renaming your DirectX 9.0b folder to just DirectX and modify your RunOnceEx to reflect that. As for your powertoys, the /qn switch will not work for these. That is for MSI installations. Edit: You'll have to search the forum for using these powertoys.

Actually, Idea Man's suggestion was the best. It will work for any folder in any view mode.

Great! glad you got it working. I wish I could have made it less confusing earlier. Drive lettering is strange. It's different when you are in dos and during the initial phase of installation then when you are actually logged into the OS. I only have one OS installed so I haven't quite grasped how that works. It sure can make things confusing. Anyway, Glad you got it going. Cheers,

Check this thread: http://www.msfn.org/board/index.php?showto...=0entry130996

Okay. Close notepad Go to Start -> Run, enter attrib -r c:\boot.ini next, go to Start -> Run, enter notepad c:\boot.ini Now, don't change anything that's currently in this file. Just add the following line to the end. Again, don't change anything else: multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP Pro Edition" /fastdetect Now save the file. Hopefully, it will let you boot into the OS on D:. If it doesn't, you will still be able to boot again into C: and we can go from there. You should end up with this: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP Pro Edition" /fastdetect Originally, you had XP Pro on one drive and Home on the other. I'm thinking now that XP home might be on both drives now. Is that correct?

We're talking about 2 different hard drives and not partitions, right?

Okay, do this: Go to Start -> Run, enter notepad c:\boot.ini. Copy what's displayed and post it here. Also, which drive (os) are you able to boot into? Does your other drive still contain your XP installation?

No Problem

I'm pretty sure this would work: [HKEY_CURRENT_USER\Control Panel\Desktop] "ScreenSaverIsSecure"="0" Edit: You might want to look through your Registry file and see if this is already in there and set it to 0.

I wouldn't think so. Honestly I'm not sure. The only way to find out is by testing.

All you had to do was remove they key from your winnt.sif and that would have been the end of it. Just trying to save you trouble. Instead, you chose to go on about generic product keys (what the hell is that?) and moral issues.

I'm not sure I understand. If it works I'm not sure what you are asking. Edit: Oh, okay. Glad it works.