jrzycrim

****, I feel old. I have an old commodore 64 stashed in the closet. It still works! Even have the old GEOS OS. (Graphic Environment Operating System). I actually had it up and running a few months ago. Played a game of Red Storm Rising. Cheers,

I'm not sure about freeware. I use Diskeeper 8 Professional. Cheers,

Really! I'd hate it if I had to share my system. I don't think I could. I can understand why he's worried about his 'puter getting screwed up. I'd be nervous all the time! For what he needs, he could probably find some pretty cheap systems that would fit the bill. Cheers,

Okay: Those shouldn't be a problem Good Luck,

Regedit stores the last key that was open in the registry. This script clears the last remembered key from the registry and opens Regedit at the top with no open keys. Dim objShell, RegKey, Q Set objShell = CreateObject("WScript.Shell") strQuote = chr(34) RegKey = "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Applets\Regedit" RegKey = RegKey & "\LastKey" objShell.RegWrite RegKey, "" objShell.Run "%systemroot%\System32\regedt32"Copy this code into a text file and save it as a .vbs file. (regedit.vbs, for example). I put mine in the windows directory and created a shortcut to it on the taskbar. I don't really like the vbs icon. Sorry If this is already on the site. I did search for it but there are a lot of tweaks here. Cheers,

Hard Drive space isn't really an issue. You probably have more than enough. I was thinking more about overall system performance. For web browsing, you don't need much. With games, depending on what games you're talking about, they might not perform so well inside the VM.

I have to agree with RaveRod. Using a VM for each user seems like a huge waste of system resources. You're definitely better off creating separate user accounts. Edit: I posted this before I saw your last post. I understand what you are trying to do. What Kind of games are we talking about here? How well will they run inside a virtual machine?

You could create a user account for each family member and then place their respective virtual machine icon in their startup folder. What's to prevent them from exiting the VM?

Found this at M$: http://support.microsoft.com/default.aspx?...8&Product=winxp Cheers,

Not exactly happy. For whatever reason, the shellstate tweak worked for me. I just wasn't sure how to apply your method until I actually looked at that inf file. Your method is definitely cleaner. Should work for anybody without all the classic menu fuss. Cheers,

Heh

No prob. Actually a good learning experience for me. I Haven't really messed around with theme/msstyles files beyond using them. I've Modified a few themes with Reshacker; Nothing major though.

The problem is the theme file you are using. [VisualStyles]Path=%WinDir%resources\Themes\MetallicShades\MetallicShades.msstylesColorStyle=NormalColorSize=NormalSizeIn this section, ColorStyle should be set to Metallic: [VisualStyles]Path=%WinDir%\resources\Themes\MetallicShades\MetallicShades.msstylesColorStyle=MetallicSize=NormalSizeThe theme/msstlyes MetallicShades doesn't understand ColorStyle=Normal. That is part of the luna theme/msstyles. Actually, NormalColor is coded into luna.msstyles. Set this to Metallic and it should work.

I downloaded the theme from ThemeXP.org and installed it. Selected it from the appearances tab, then saved the theme from the Themes tab. I reverted back to my usual theme, then loaded the new theme file which I created. It worked fine. I doubt it's a problem with the msstyles file if you can set it manually. Good Luck

Componants should be Components

LOL! I just took a peak at gosh's site and tried this based on the Install4.inf. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer]"ConfirmFileDelete"=dword:00000000 This seems to work much better then mucking about with shellstate. Great site gosh.

I'm sure that this will vary from system to system depending on a users particular settings. Of course, I have no clue what the actual numbers represent. C is 12 in hexadecimal, which is how these values are represented. So, as you suggest, each user should export that key for their own system. Beyond that, I don't know. Edit: I did find this page that relates: XP Start Menu Style They mention the following reg key: I tested this out on my system and Rebooted. It didn't make a difference.

Very Strange... I do have that as part of my unnattended install. As far as testing that before I posted, I did just merge that into the regestry after setting the delete confirmation on. It didn't change anything back to classic, however. The only thing I can think of is maybe the theme file I load during installation is changing it back to the new style menu/desktop. Or possibly I have something else in my registy tweaks that is doing it. I'll have to look at my reg file... Cheers, Jim

Guuz, did you get it working yet? If not, try double-clicking the msstyles file. Normally, that will bring up the display properties/appearance tab. From there, you should be able to adjust that style and then from the themes tab, save your theme.

Weird. I don't use the classic start menu. I've used that for some time now and haven't had that problem. Even tested that key before I posted. I manually set the delete confirmation and then applied that tweak. Not sure what the problem is.

If a line of data needs to wrap to the next line, the backslash (\) character is used to indicate a continuation on the following line. If you look closely, the registry code you posted is not exactly the same. Good Luck, Jim

It disabled the delete confirmation and did not revert to to the windows classic theme.

did you try what I posted? It works on my end...

;-Disable Delete Confirmation (Recycle Bin)[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer]"ShellState"=hex:24,00,00,00,37,88,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\ 01,00,00,00,0d,00,00,00,00,00,00,00,01,00,00,00I just tested this and it works.

No, an unattended cd is not a recovery cd. It's a normal installation CD that does not require user intervention. See Unattended XP CD Guide