Takeshi

Apart from fast user switching, I don't know what else it is, or the logic behind it. If it's FSW, then there's a reg key... HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon AllowMultipleTSSessions REG_DWORD: 1

v.03 already! quite impressed with your effort

Nice app. The forum download link still points to WISCON_v01.zip.

It it's VLK, when you try to activate, the activation window will just say it's activated without further action.

You don't have the Security Tab when logged in as admin because you have Simple File Sharing enabled in your XP Pro computer. The file and folder's ACL is not stored in the registry but as a security descriptor in the file. The ACL contains a list of ACEs (access control entries) and the SIDs of the security principals. The logon scripts can be controlled via Group Policy but they shouldn't be really necessary to apply folder permissions or policies, unless you mean roaming profiles in a domain.

That's what I thought after reading the MS KB and TechNet articles, but the MSFN Guide says it's needed (in the SVCPACK.INF Method section). Perhaps it needs updating or clarification. On a related note, are Type 2 hotfixes not released any more?

First, decide if you need to use Simplified Chinese (as used in PRC) or Traditional Chinese (as used in Taiwan, HongKong etc.), or both. The locale ID combos that begin with 0404 all use Trad. Chi, whereas those beginning with 0804 Simplified Chi. Next, decide on the IME. IME is just a method of inputting the same written language; people have different preferences on what they like. Most users of Trad Chinese, for example, know ChengJie or Phonetic IME. Normally a user only uses one or two IMEs. That's not quite true. You need to install a specific IME in Regional Languages when you need it. If you install any one CJK language (Chi/Jap/Korean) in uA, Setup will automatically install Files for E Asian Languages.

Thanks for that! Looks good for Wi-Fi support!

I see, thanks. So it will work for domain and workgroup? Please tell me the details of this reg hack. Much appreciated!

Thanks for the replies. The DHCP and alternate config should not be a problem here. The ForensiT User Profile Wizard might be useful but not sure if it addresses the question; perhaps I didn't put it clearly. But I'll certainly give it a try. Under System Properties > Computer Name you choose whether it's a Member of Domain or Workgroup. What I'm really after is, can this be easily switched over, from domain to workgroup and vice versa?

I have a laptop (XP Pro SP2) which needs to join two different networks (Win 2000 Server domain in one, Win XP workgroup in another) at different places and at different time, what is the best way for doing this? Obviously I don't want to re-run the Network Setup Wizard everytime I change network. Any suggestions please!

The double negatives can be confusing; basically [NoInstrumentation = 1] means Windows will not track your program usage. You can just delete the policy subkey if you want Windows to behave as default; leaving it as 0 doesn't do anything (and causes confusion). But that's just me not wanting to leave useless keys hanging around. It looks you have imported someone else's reg tweak.

If you have XP SP2, use the newest version of Deploy tools, which can be downloaded from M$ (if not on the CD). M$ also has many articles on Sysprep (and numerous KB articles on problems and limitations) - well worth having a look. These will get you going: http://support.microsoft.com/default.aspx?...kb;en-us;302577 http://www.microsoft.com/technet/prodtechn...oy/default.mspx http://www.microsoft.com/technet/prodtechn...troductoin.mspx And be sure to test everything on a non-production computer first. If you have the VLK, you can use sysprep.inf to automate part of the Mini-Setup.

What did you actually do? When in the uA did you apply the reg?I said that is one of the locations. There seems to be others. I think these are character set (code pages) in the old days; not sure if these are still used nowadays.

A lot of custom menu extensions have their own CLSIDs in the registry (also under HKCR) and many subkeys refer to these CLSIDs. Have you tried doing this?

The list of Frequently Used Programs on the bottom L of the Start Menu is indeed stored in the registry but it only gets populated when you have actually run a program on the installation. This is one of the locations: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\StartPage There is already a thread with a list of input locale IDs in this forum so have a look. It's also on the MS website.

REGEDIT32.EXE should be: regedit.exe (or if you insist, regedt32.exe) There is no regedit32.exe!

It sounds like the Wireless NIC might have developed a problem, but it's worth trying to enable SSID in the first instance - sometimes this can cause problems (but then it worked before). Or do without WEP just for testing. The other thing I'd try is to use wired connection to the router and see what happens - this would narrow things down a bit.

If it's the Desktop tab in Desktop > Display Properties, then it's a policy reg key: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\System NoDispBackgroundPage Just delete it this subkey. In fact anything else there is probably put in without your consent. If in doubt, post your reg key details here. If you do decide to take the plunge to do a repair installation, bear in mind that you will have to reinstall all the subsequent hotfixes (and SP2 if your CD isn't SP2) and most programmes. So it's worth a try of the above simple measure first.

not keen on the green colour at all!

I only know the method for XP, not sure if it's the same with 2003, have a look in the registry if the same key exists and try it: http://support.microsoft.com/default.aspx?...kb;en-us;318378

If I remember correctly, authentication should be "open". More details: http://www.microsoft.com/technet/prodtechn...n/wifisoho.mspx However, if your hardware supports it and you have XP SP2, use WPA. Avoid WEP. I use NetGear, XP SP2 and WPA works effectively.

http://support.microsoft.com/kb/875352/ If you don't know how to edit or repair the boot.ini, you can logon to the Recovery Console and use the bootcfg /rebuild command. It will detect all the Windows installations and add valid entries for you.

I know it's in W2kS CD but can't find it in the XP CD.

You have to specify the locale ID for the specific IME, not just "Mandarin". If you include the correct Language and Language Group for CJK languages in winnt.sif Setup will also install Files for East Asian Languages. Language Group 9 = Trad Chi 10 = Simp. Chi See my list: http://www.msfn.org/board/index.php?showto...ndpost&p=288617