Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

I want to rename/reorganize the whole xp 'shell folders' and &

- - - - -

  • Please log in to reply
5 replies to this topic

#1
frf954

frf954
  • Member
  • 8 posts
  • OS:XP Home
  • Country: Country Flag
Hello,I just reinstalled my windows xp sp2 home edition that come with my dell pc,
this is a french version. And I got fed up with it's default organization
so I want to make it clearer like this:

H:\users\all
H:\users\default
H:\users\winuser
H:\users\localservice
H:\users\networkservice

H:\users\all\!_appdata
H:\users\all\!_appdata\Microsoft
H:\users\all\!_appdata\Microsoft\Crypto
H:\users\all\!_appdata\Microsoft\Crypto\DSS
H:\users\all\!_appdata\Microsoft\Crypto\RSA
H:\users\all\!_appdata\Microsoft\Crypto\DSS\MachineKeys
H:\users\all\!_appdata\Microsoft\Crypto\RSA\MachineKeys
H:\users\all\!_appdata\Microsoft\Crypto\RSA\S-1-5-18
H:\users\all\!_appdata\Microsoft\HTML Help
H:\users\all\!_appdata\Microsoft\Media Index
H:\users\all\!_appdata\Microsoft\Media Player
H:\users\all\!_appdata\Microsoft\Network
H:\users\all\!_appdata\Microsoft\Network\Connections
H:\users\all\!_appdata\Microsoft\Network\Connections\Cm
H:\users\all\!_appdata\Microsoft\Network\Connections\Pbk
H:\users\all\!_appdata\Microsoft\User Account Pictures
H:\users\all\!_appdata\Microsoft\User Account Pictures\Default Pictures
H:\users\all\!_appdata\Prism
H:\users\all\!_desktop
H:\users\all\!_startmenu
H:\users\all\!_startmenu\programs
H:\users\all\!_startmenu\programs\accessories
H:\users\all\!_startmenu\programs\accessories\Accessibility
H:\users\all\!_startmenu\programs\accessories\communications
H:\users\all\!_startmenu\programs\accessories\entertainment
H:\users\all\!_startmenu\programs\accessories\system_tools
H:\users\all\!_startmenu\programs\administration_tools
H:\users\all\!_startmenu\programs\games
H:\users\all\!_startmenu\programs\Modem Helper
H:\users\all\!_startmenu\programs\Modem On Hold
H:\users\all\!_startmenu\programs\Powertoys for Windows XP
H:\users\all\!_startmenu\programs\startup
H:\users\all\a_favorites
H:\users\all\a_models
H:\users\all\a_shared_documents
H:\users\all\a_shared_images
H:\users\all\a_shared_music
H:\users\all\a_music\playlists
H:\users\all\a_music\music_samples
H:\users\all\a_music\sample_playlists
H:\users\all\a_music\sample_playlists\000D5E0E
H:\users\all\a_images\images_samples
H:\users\all\DRM

H:\users\default\!_appdata
H:\users\default\!_appdata\Microsoft
H:\users\default\!_appdata\Microsoft\Internet Explorer
H:\users\default\!_appdata\Microsoft\Media Player
H:\users\default\!_appdata\Microsoft\SystemCertificates
H:\users\default\!_appdata\Microsoft\SystemCertificates\My
H:\users\default\!_appdata\Microsoft\SystemCertificates\My\Certificates
H:\users\default\!_appdata\Microsoft\SystemCertificates\My\CRLs
H:\users\default\!_appdata\Microsoft\SystemCertificates\My\CTLs
H:\users\default\!_cookies
H:\users\default\!_desktop
H:\users\default\!_local_s
H:\users\default\!_local_s\!_appdata
H:\users\default\!_local_s\!_appdata\Microsoft
H:\users\default\!_local_s\!_appdata\Microsoft\Media Player
H:\users\default\!_local_s\!_appdata\Microsoft\Windows Media
H:\users\default\!_local_s\!_appdata\Microsoft\Windows Media\9.0
H:\users\default\!_local_s\!_history
H:\users\default\!_local_s\!_history\History.IE5
H:\users\default\!_local_s\!_temp
H:\users\default\!_local_s\!_tempintfls
H:\users\default\!_local_s\!_tempintfls\Content.IE5
H:\users\default\!_models
H:\users\default\!_nethood
H:\users\default\!_printhood
H:\users\default\!_sendto
H:\users\default\!_startmenu
H:\users\default\!_startmenu\programs
H:\users\default\!_startmenu\programs\accessories
H:\users\default\!_startmenu\programs\startup
H:\users\default\!_startmenu\programs\accessories\Accessibility
H:\users\default\!_startmenu\programs\accessories\entertainment
H:\users\default\m_documents
H:\users\default\m_favoris
H:\users\default\m_recent

H:\users\winuser\!_appdata
H:\users\winuser\!_appdata\Identities
H:\users\winuser\!_appdata\Microsoft
H:\users\winuser\!_appdata\Microsoft\Credentials
H:\users\winuser\!_appdata\Microsoft\CryptnetUrlCache
H:\users\winuser\!_appdata\Microsoft\Crypto
H:\users\winuser\!_appdata\Microsoft\HTML Help
H:\users\winuser\!_appdata\Microsoft\IMJP8_1
H:\users\winuser\!_appdata\Microsoft\Internet Explorer
H:\users\winuser\!_appdata\Microsoft\Media Player
H:\users\winuser\!_appdata\Microsoft\MMC
H:\users\winuser\!_appdata\Microsoft\Protect
H:\users\winuser\!_appdata\Microsoft\SystemCertificates
H:\users\winuser\!_appdata\Microsoft\Windows
H:\users\winuser\!_appdata\Microsoft\CryptnetUrlCache\Content
H:\users\winuser\!_appdata\Microsoft\CryptnetUrlCache\MetaData
H:\users\winuser\!_appdata\Microsoft\Crypto\RSA
H:\users\winuser\!_appdata\Microsoft\Internet Explorer\Quick Launch
H:\users\winuser\!_appdata\Microsoft\SystemCertificates\My
H:\users\winuser\!_appdata\Microsoft\SystemCertificates\My\Certificates
H:\users\winuser\!_appdata\Microsoft\SystemCertificates\My\CRLs
H:\users\winuser\!_appdata\Microsoft\SystemCertificates\My\CTLs
H:\users\winuser\!_appdata\Microsoft\Windows\Themes
H:\users\winuser\!_cookies
H:\users\winuser\!_desktop
H:\users\winuser\!_favorites
H:\users\winuser\!_favorites\Liens
H:\users\winuser\!_local_s
H:\users\winuser\!_local_s\!_temp
H:\users\winuser\!_local_s\!_tempintfls
H:\users\winuser\!_local_s\!_tempintfls\Content.IE5
H:\users\winuser\!_local_s\!_tempintfls\Content.IE5\GDMF8XQF
H:\users\winuser\!_local_s\!_tempintfls\Content.IE5\WDUZOHYZ
H:\users\winuser\!_local_s\!_tempintfls\Content.IE5\WHUN0TA7
H:\users\winuser\!_local_s\!_tempintfls\Content.IE5\WPYN0HIJ
H:\users\winuser\!_nethood
H:\users\winuser\!_printhood
H:\users\winuser\!_sendto
H:\users\winuser\!_startmenu
H:\users\winuser\!_startmenu\programs
H:\users\winuser\!_startmenu\programs\accessories
H:\users\winuser\!_startmenu\programs\accessories\accessibility
H:\users\winuser\!_startmenu\programs\accessories\entertainment
H:\users\winuser\!_startmenu\programs\startup
H:\users\winuser\!_templates
H:\users\winuser\!_userdata
H:\users\winuser\m_documents
H:\users\winuser\m_dowloads
H:\users\winuser\m_images
H:\users\winuser\m_music
H:\users\winuser\m_videos
H:\users\winuser\m_recent

H:\users\localservice\!_appdata
H:\users\localservice\!_appdata\Microsoft
H:\users\localservice\!_appdata\Microsoft\Credentials
H:\users\localservice\!_appdata\Microsoft\Internet Explorer
H:\users\localservice\!_appdata\Microsoft\Media Player
H:\users\localservice\!_appdata\Microsoft\SystemCertificates
H:\users\localservice\!_appdata\Microsoft\Credentials\S-1-5-19
H:\users\localservice\!_appdata\Microsoft\SystemCertificates\My
H:\users\localservice\!_appdata\Microsoft\SystemCertificates\My\Certificates
H:\users\localservice\!_appdata\Microsoft\SystemCertificates\My\CRLs
H:\users\localservice\!_appdata\Microsoft\SystemCertificates\My\CTLs
H:\users\localservice\!_cookies
H:\users\localservice\!_local_s
H:\users\localservice\!_local_s\appdata
H:\users\localservice\!_local_s\appdata\Microsoft
H:\users\localservice\!_local_s\appdata\Microsoft\Credentials
H:\users\localservice\!_local_s\appdata\Microsoft\Windows
H:\users\localservice\!_local_s\appdata\Microsoft\Credentials\S-1-5-19
H:\users\localservice\!_local_s\history
H:\users\localservice\!_local_s\History\History.IE5
H:\users\localservice\!_local_s\temp
H:\users\localservice\!_local_s\tempintfls
H:\users\localservice\!_local_s\tempintfls\Content.IE5
H:\users\localservice\!_local_s\tempintfls\Content.IE5\41YZOX6J
H:\users\localservice\!_local_s\tempintfls\Content.IE5\KHYVCXMF
H:\users\localservice\!_local_s\tempintfls\Content.IE5\SXQRK9UR
H:\users\localservice\!_local_s\tempintfls\Content.IE5\WHIB456N

H:\users\networkservice\!_appdata
H:\users\networkservice\!_appdata\Microsoft
H:\users\networkservice\!_appdata\Microsoft\Credentials
H:\users\networkservice\!_appdata\Microsoft\Internet Explorer
H:\users\networkservice\!_appdata\Microsoft\Media Player
H:\users\networkservice\!_appdata\Microsoft\SystemCertificates
H:\users\networkservice\!_appdata\Microsoft\Credentials\S-1-5-20
H:\users\networkservice\!_appdata\Microsoft\SystemCertificates\My
H:\users\networkservice\!_appdata\Microsoft\SystemCertificates\My\Certificates
H:\users\networkservice\!_appdata\Microsoft\SystemCertificates\My\CRLs
H:\users\networkservice\!_appdata\Microsoft\SystemCertificates\My\CTLs
H:\users\networkservice\!_cookies
H:\users\networkservice\!_local_s
H:\users\networkservice\!_local_s\appdata
H:\users\networkservice\!_local_s\appdata\Microsoft
H:\users\networkservice\!_local_s\appdata\Microsoft\Credentials
H:\users\networkservice\!_local_s\appdata\Microsoft\Windows
H:\users\networkservice\!_local_s\appdata\Microsoft\Credentials\S-1-5-20
H:\users\networkservice\!_local_s\history
H:\users\networkservice\!_local_s\history\History.IE5
H:\users\networkservice\!_local_s\Temp
H:\users\networkservice\!_local_s\tempintfls
H:\users\networkservice\!_local_s\tempintfls\Content.IE5
H:\users\networkservice\!_local_s\tempintfls\Content.IE5\4TM3GDU3
H:\users\networkservice\!_local_s\tempintfls\Content.IE5\5WV2IWXY
H:\users\networkservice\!_local_s\tempintfls\Content.IE5\E1K3MNO7
H:\users\networkservice\!_local_s\tempintfls\Content.IE5\STI7CXA3

H:\programs\!_common_files
H:\programs\!_common_files\InstallShield
H:\programs\!_common_files\Microsoft Shared
H:\programs\!_common_files\MSSoap
H:\programs\!_common_files\ODBC
H:\programs\!_common_files\Services
H:\programs\!_common_files\SpeechEngines
H:\programs\!_common_files\System
H:\programs\!_common_files\InstallShield\Driver
H:\programs\!_common_files\InstallShield\Engine
H:\programs\!_common_files\InstallShield\IScript
H:\programs\!_common_files\InstallShield\Professional
H:\programs\!_common_files\InstallShield\Driver\7
H:\programs\!_common_files\InstallShield\Driver\7\Intel 32
H:\programs\!_common_files\InstallShield\Engine\6
H:\programs\!_common_files\InstallShield\Engine\6\Intel 32
H:\programs\!_common_files\InstallShield\Professional\RunTime
H:\programs\!_common_files\InstallShield\Professional\RunTime\09
H:\programs\!_common_files\InstallShield\Professional\RunTime\10
H:\programs\!_common_files\InstallShield\Professional\RunTime\09\01
H:\programs\!_common_files\InstallShield\Professional\RunTime\09\01\Intel32
H:\programs\!_common_files\InstallShield\Professional\RunTime\10\01
H:\programs\!_common_files\InstallShield\Professional\RunTime\10\50
H:\programs\!_common_files\InstallShield\Professional\RunTime\10\01\Intel32
H:\programs\!_common_files\InstallShield\Professional\RunTime\10\50\Intel32
H:\programs\!_common_files\Microsoft Shared\DAO
H:\programs\!_common_files\Microsoft Shared\MSInfo
H:\programs\!_common_files\Microsoft Shared\Papier … lettres
H:\programs\!_common_files\Microsoft Shared\Speech
H:\programs\!_common_files\Microsoft Shared\TextConv
H:\programs\!_common_files\Microsoft Shared\Triedit
H:\programs\!_common_files\Microsoft Shared\VGX
H:\programs\!_common_files\Microsoft Shared\Web Folders
H:\programs\!_common_files\Microsoft Shared\web server extensions
H:\programs\!_common_files\Microsoft Shared\Speech\1036
H:\programs\!_common_files\Microsoft Shared\web server extensions\40
H:\programs\!_common_files\Microsoft Shared\web server extensions\40\_vti_bin
H:\programs\!_common_files\Microsoft Shared\web server extensions\40\admcgi
H:\programs\!_common_files\Microsoft Shared\web server extensions\40\admisapi
H:\programs\!_common_files\Microsoft Shared\web server extensions\40\bin
H:\programs\!_common_files\Microsoft Shared\web server extensions\40\bots
H:\programs\!_common_files\Microsoft Shared\web server extensions\40\isapi
H:\programs\!_common_files\Microsoft Shared\web server extensions\40\servsupp
H:\programs\!_common_files\Microsoft Shared\web server extensions\40\admcgi\scripts
H:\programs\!_common_files\Microsoft Shared\web server extensions\40\admisapi\scripts
H:\programs\!_common_files\Microsoft Shared\web server extensions\40\bin\1036
H:\programs\!_common_files\Microsoft Shared\web server extensions\40\bots\vinavbar
H:\programs\!_common_files\Microsoft Shared\web server extensions\40\isapi\_vti_adm
H:\programs\!_common_files\Microsoft Shared\web server extensions\40\isapi\_vti_aut
H:\programs\!_common_files\Microsoft Shared\web server extensions\40\_vti_bin\_vti_adm
H:\programs\!_common_files\Microsoft Shared\web server extensions\40\_vti_bin\_vti_aut
H:\programs\!_common_files\MSSoap\Binaries
H:\programs\!_common_files\MSSoap\Binaries\Resources
H:\programs\!_common_files\MSSoap\Binaries\Resources\1036
H:\programs\!_common_files\ODBC\Data Sources
H:\programs\!_common_files\SpeechEngines\Microsoft
H:\programs\!_common_files\SpeechEngines\Microsoft\Lexicon
H:\programs\!_common_files\SpeechEngines\Microsoft\TTS
H:\programs\!_common_files\SpeechEngines\Microsoft\Lexicon\1033
H:\programs\!_common_files\SpeechEngines\Microsoft\TTS\1033
H:\programs\!_common_files\System\ado
H:\programs\!_common_files\System\msadc
H:\programs\!_common_files\System\Ole DB
H:\programs\ComPlus Applications
H:\programs\CONEXANT
H:\programs\Digital Line Detect
H:\programs\InstallShield Installation Information
H:\programs\Intel
H:\programs\Internet Explorer
H:\programs\Messenger
H:\programs\microsoft frontpage
H:\programs\Modem Helper
H:\programs\Modem On Hold
H:\programs\Movie Maker
H:\programs\MSN
H:\programs\MSN Gaming Zone
H:\programs\NetMeeting
H:\programs\Online Services
H:\programs\Outlook Express
H:\programs\Services en ligne
H:\programs\Uninstall Information
H:\programs\Windows Media Player
H:\programs\Windows NT
H:\programs\WindowsUpdate
H:\programs\xerox
H:\programs\Intel\INFInst
H:\programs\Internet Explorer\Connection Wizard
H:\programs\Internet Explorer\PLUGINS
H:\programs\Internet Explorer\SIGNUP
H:\programs\microsoft frontpage\version3.0
H:\programs\microsoft frontpage\version3.0\bin
H:\programs\Movie Maker\MUI
H:\programs\Movie Maker\Shared
H:\programs\Movie Maker\MUI\040C
H:\programs\Movie Maker\Shared\Profiles
H:\programs\MSN\MSNCoreFiles
H:\programs\MSN\MSNCoreFiles\Install
H:\programs\MSN\MSNCoreFiles\Install\MSN9Components
H:\programs\MSN Gaming Zone\Windows
H:\programs\Windows Media Player\Icons
H:\programs\Windows Media Player\Sample Playlists
H:\programs\Windows Media Player\Skins
H:\programs\Windows Media Player\Visualizations
H:\programs\Windows NT\Accessoires
H:\programs\Windows NT\Pinball
H:\programs\xerox\nwwia

I think I will do this by using scripts and reg files but I don't want to redo this
every time I reinstall windows.

1- Can I do this for all the folders I wan't to rename?

2- Should I use nLite to make this?

3- Will I be able to rename all the folder I want with nLite?

4- Will I have to use a script with nLite?

5- Is it simply possible?

[EDIT] I am sorry if it not the right section but I don't know in which section it belong exactly.

Edited by frf954, 08 July 2012 - 11:24 AM.



How to remove advertisement from MSFN

#2
Ponch

Ponch

    MSFN Junkie

  • Patrons
  • 3,262 posts
  • OS:none specified
  • Country: Country Flag
2-3-4; nLite will only let you rename "Documents and Settings" and "Program Files" (or their french equivalent), which is about half a percent of what you want to do. Also nLite is for personal use only (in case this is work related)
You will need deep search to modify the source. Maybe you can find more info in the "Unattended XP". Not sure.

#3
CharlotteTheHarlot

CharlotteTheHarlot

    MSFN Master

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,054 posts
  • OS:none specified
  • Country: Country Flag

Hello,I just reinstalled my windows xp sp2 home edition that come with my dell pc, this is a french version. And I got fed up with it's default organization so I want to make it clearer like this:

H:\users\all
H:\users\default
H:\users\winuser
H:\users\localservice
H:\users\networkservice

H:\programs\!_common_files


I think I will do this by using scripts and reg files but I don't want to redo this every time I reinstall windows.

1- Can I do this for all the folders I wan't to rename?
2- Should I use nLite to make this?
3- Will I be able to rename all the folder I want with nLite?
4- Will I have to use a script with nLite?
5- Is it simply possible?


Funny thing is that I was just thinking out loud in another thread about how great it would have been if Microsoft had done this for WinXP. Let me first admit that I have never tried retro-fitting the new Windows 6 (Vista/7) profile strategy to Windows 5 (e.g., WinXP). I have always thought it was theoretically possible but still have not found the time to experiment. So I will not be able to offer anything except perhaps vague, marginally useful, philosophical rambling here. Presuming you are confining it to the simpler 32-bit model, In a nutshell, is this your goal? ...

C:\Documents and Settings ---> C:\Users
C:\Program Files ------------> C:\Programs


Also, what do you mean by "using scripts"? Do you mean VB or Powershell scripts using external commands like REG.EXE? Or are you referring to Registry scripts (.REG) to be imported? If it is the latter, and you are thinking about editing all occurrences of C:\Documents and Settings (plus all the possible short filename permutations e.g., DOCUME~1, perhaps complicated with French translation) and then importing the corrections, well, this begs another question. Do you know what registry Expand_SZ data types are? I guarantee you will be learning all about them if you don't know already.

Backing up a bit, let's consider that broadly there are two ways to approach this heart transplant:

(1) Altering an existing working WinXP installation after the fact.

(2) Modifying the setup files to fresh install it correctly in the first place.


IMHO, the strategy with the highest probably of success (mentioned by Ponch) is probably (2) and I suspect it will involve more than just using nLite. I expect this will mean completely copying the WinXP CDROM to folders on the HDD, integrate the SP3 if not done already, and THEN search INF files (and perhaps every single file on disk) for strings like Profile ProfilesDirectory ProgramFiles CommonDir as well as Documents and Settings and also Docume~1 and Program Files and also Progra~1. After all, this is Microsoft we are talking about, or should I say Micros~1. :lol: If you are lucky (well, me too since I would really like to try this) then perhaps some Google research may find someone that has already identified all the points of change that need editing. My guess is that it will probably be necessary to first search for SystemRoot in order to identify the vectors where Windows setup first initializes the variables for later use in the setup process. I suspect it may happen in more than one location. I can't remember if there is one variable in WinXP that singlehandedly sets it correctly, i.e., ProfilesDirectory = C:\Users. A quick look at Google did not give me any assurance that there is an easy way to accomplish this.

Now, method (1) breaks down two more ways. One is theoretically simple, (1a) just adding a new user to the system (using the new C:\Users path you want) after you have somehow successfully changed the environment variables to point to the new physical path on disk. The other way, (1b) changing all existing accounts (including SYSTEM, etc) is much harder, perhaps impossible. I have often thought about the logistics of this, it is a giant undertaking because the Registry is loaded with references to the x:\Docume... convention, lots of them are in plain sight in normal Strings, but the more important ones are in Expand_SZ. Compounding this is the fact that sometimes paths with variables are found in normal strings as well as Expanded strings. Add to this the exponential complicator the tilde (~) possibilities. And don't forget to mount the registries of all the other existing users since they will also have references to correct. So there are many things to cover in doing the (.REG) import fixing. A quick checklist of possibilities (subject to later editing if someone thinks of something I forget) of data to search for ...

Normal Strings containing only variables %UserProfile% etc (*)
Normal Strings containing only paths C:\Documents and Settings
Normal Strings containing only paths C:\Docume~1
Normal Strings containing both %SystemDrive%\Documents and Settings
Normal Strings containing both %SystemDrive%\Docume~1

Expand_SZ containing only variables %UserProfile% etc (*)
Expand_SZ containing only paths C:\Documents and Settings
Expand_SZ containing only paths C:\Docume~1
Expand_SZ containing both %SystemDrive%\Documents and Settings
Expand_SZ containing both %SystemDrive%\Docume~1

(*) Paths that only use variables would be OK once the global variables have been corrected.

Some people might wonder why variables like %ProgramFiles% or %UserProfile% or %SystemRoot% would even appear in a normal string because ideally it shouldn't. Well it can. It all depends on the author of some program and what he chose for the registry data type and as long as his function expands the variable as needed then he can store it however he wants to. For example, %SystemRoot% and %UserProfile% are found in plain text in INI files by programs that expand variables themselves. They are also found in places like plain text theme (.THE .THEME) files.

Some people might wonder why fully qualified paths (with or without ~tilde~) but without system variables are found in Expand_SZ strings. There is simply no good reason for it, but programmers are fickle. Some think they are getting free quasi-encryption which somehow protects them from casual users looking at the plain text of a registry export. Others might have just made a mistake. Murphy's law of computers again, given a set of rules every possible permutation of combinations will eventually exist. (~sigh~).

Remember that the case can be mixed. So searching needs to be case-insensitive. This rules out searching a registry export for expanded strings (assuming you know the hex equivalents for the spelling of the path. This kind of search needs to be done live in REGEDIT or an equivalent tool like Registry Workshop or something else. Once again, extra user hives need to be mounted.

Remember that any part of a path with more than eight characters might have a ~tilde~. This leads to exponential variation like Program Files\Common Files and Progra~1\Common Files and Program Files\Common~1 and Progra~1\Common~1 or more if the paths below are long filenames! Mathematically it is 2^2 = 4 different possibilities just for these two levels. Three levels deep is 2^3 = 8 and four is 2^4 = 16 and so on! Of course that is limiting it to ~1 and not the case of ~2 which would really suck! Therefore the two search strings that will cover the most territory in a single pass is probably these ... \Docume ... and ... \Progra

Unfortunately this does not end at the registry. It is entirely possible for many files to also reference variables SystemRoot etc ... and/or strings with C:\Documents and Settings ... and/or strings with C:\Docume~1. INI files for example and CFG and BAT and CMD and LNK and INF and etc. As mentioned above, THEME files will often have variables, but they also work just fine with full paths. Therefore a brute force search of every file on an entire hard-disk will be the only sure way to locate every reference. As daunting as this sounds, the good news is that the 2nd pass and 3rd pass is much faster than the 1st pass apparently because of improved caching in memory of recent disk data between Win9x and WinXP. This can be demonstrated by doing a directory filelist twice, ex: dir c:\*.* /a /s > Filelist.txt. The first one is murder, the second one much better.

You asked about renaming the User profiles after all the changes were completed. I would instead first do straight copies and rename the copies. Leave the originals for a while. Unfortunately it is impossible to perfectly copy the profiles while you are running. This means booting up in an independent OS and accessing the disk containing your Windows install remotely to copy the profiles, or dropping the disk in another computer and copying them that way. This is an offline job to be done by something like DaRT or unofficial equivalent.

All of a sudden method (2) looks much better than method (1). :thumbup But please note, I am NOT trying to talk you out of it, just pointing out some of the potential trouble along the way.

Overall, I do believe this idea (method (2)) has merit because this is one area where a Windows XP design flaw was successfully corrected in later versions (and then they blew it again with C:\Program Files (x86) anyway. Let's not even discuss the Wow64 and System32 logic either). If I can find the time I will do what I suggest and expand an SP3 CDROM to a folder and brute force scan every file as I suggested and post a list that I find. Unfortunately I just thought of another problem, it is probably the case where some compressed files (i.e., Something.inf compressed as Something.in_) contain references that need edits. Such references will not be found in even a brute force file search. This could become quite the project if it involves expanding every file in the \i386 folders and probably even those found in .cab archives. Yikes! This means to create a complete inventory of every file path reference potentially used by Windows XP setup will necessitate a complete expansion of every file and cabinet. Then, locating the files, editing them and recompressing them and/or re-inserting them in cabinets (with possible checksum problems?). Finally, all of this may need to be done multiple times depending on the differences between Retail and OEM, Home and Pro, and even official MSDN SP3 Final versus SP3 applied to one of the other public flavors. I hope some others who have done some research here can comment and offer their own insight!

EDIT: fixing my own stupid mistakes

Edited by CharlotteTheHarlot, 09 July 2012 - 05:28 PM.

... Let him who hath understanding reckon the Number Of The Beast ...


#4
frf954

frf954
  • Member
  • 8 posts
  • OS:XP Home
  • Country: Country Flag

Funny thing is that I was just thinking out loud in another thread about how great it would have been if Microsoft had done this for WinXP. Let me first admit that I have never tried retro-fitting the new Windows 6 (Vista/7) profile strategy to Windows 5 (e.g., WinXP). I have always thought it was theoretically possible but still have not found the time to experiment. So I will not be able to offer anything except perhaps vague, marginally useful, philosophical rambling here. Presuming you are confining it to the simpler 32-bit model, In a nutshell, is this your goal? ...

C:\Documents and Settings ---> C:\Users
C:\Program Files ------------> C:\Programs


Also, what do you mean by "using scripts"? Do you mean VB or Powershell scripts using external commands like REG.EXE? Or are you referring to Registry scripts (.REG) to be imported? If it is the latter, and you are thinking about editing all occurrences of C:\Documents and Settings (plus all the possible short filename permutations e.g., DOCUME~1, perhaps complicated with French translation) and then importing the corrections, well, this begs another question. Do you know what registry Expand_SZ data types are? I guarantee you will be learning all about them if you don't know already.

Backing up a bit, let's consider that broadly there are two ways to approach this heart transplant:

(1) Altering an existing working WinXP installation after the fact.

(2) Modifying the setup files to fresh install it correctly in the first place.


IMHO, the strategy with the highest probably of success (mentioned by Ponch) is probably (2) and I suspect it will involve more than just using nLite. I expect this will mean completely copying the WinXP CDROM to folders on the HDD, integrate the SP3 if not done already, and THEN search INF files (and



First of all thank for this reply CharlotteTheHarlot I understand the problem better now. My goal is as you guessed to rearrange it so as it looks more like Windows7 or Linux naming strategy, more exactly what I want to do is:
1- shorten paths.
2- remove or replace spaces by underscore.
3- convert all to lowercase.
4- add prefixes like '!_' or 'm_' in order to recognize them faster or to have them sorted automatically in name sorting.
5- Another problem in my french version is that it mix both languages so I stick to english because it's shorter most of the time.
6- Simplify the tree structure like for 'my documents' 'my image' 'my music' 'my videos'
7- And I think it's all

So for example some of the folder I want to rename in the main user:

//user's folders needed by the system and present at the instalation or creation of the profile.
H:\users\winuser\!_appdata
H:\users\winuser\!_cookies
H:\users\winuser\!_desktop
H:\users\winuser\!_favorites
H:\users\winuser\!_local_s
H:\users\winuser\!_local_s\!_temp
H:\users\winuser\!_local_s\!_tempintfls
H:\users\winuser\!_nethood
H:\users\winuser\!_printhood
H:\users\winuser\!_sendto
H:\users\winuser\!_startmenu
H:\users\winuser\!_startmenu\programs
H:\users\winuser\!_startmenu\programs\accessories
H:\users\winuser\!_startmenu\programs\accessories\accessibility
H:\users\winuser\!_startmenu\programs\accessories\entertainment
H:\users\winuser\!_startmenu\programs\startup
H:\users\winuser\!_templates
H:\users\winuser\!_userdata

// user's personals folders... "m_" or whatever.
H:\users\winuser\m_documents
H:\users\winuser\m_dowloads
H:\users\winuser\m_images
H:\users\winuser\m_music
H:\users\winuser\m_videos
H:\users\winuser\m_recent


so yes for example
C:\Documents and Settings ---> C:\Users
C:\Program Files ------------> C:\Programs

C:\Documents and Settings\Application Data -----> C:\users\!_appdata

C:\Documents and Settings\My Documents -----> C:\users\m_documents


Another complexity is that I want to separate some of those folders over several partitions over 2 hard drives:

[HD1---256 Gb] : (files with a lot of writing/rewriting cycle that defragment a lot)
part1---windows swap (pagefile)
part2---C:\Documents and Settings\Application Data -----> C:\users\!_appdata
part2---C:\Documents and Settings\Local Settings -----> C:\users\!_local_s
part2---C:\RECYCLER maybe
part2---restoration files maybe
partX---plus some partitions for linux or shared

[HD2---1000 Gb] : (All OS; winXP,seven,distroLinux1,distroLinux2...; and personal static data storage for C:\users\ and linux /home/ )
part1---windows XP
part2---Distro Linux 1
(...)
partX---windows C:\users\ C:\programs
partX---plus some linux


I will expose this in a different topic maybe so keep this short. All this to avoid a lot of defragmention but the problem will be to remount all those folders after windows reinstallation. So that why I would prefer create a nLited CD or whatever unattended CD with all thoses fixes.

I was meaning by "using scripts" that I have not choosed script type yet. However this method seems compromised to me regarding what you have written. I also think the brute force method has the best chance of sucess but unless someone create a new nLite like program that is able to do this, I am not seeing this anytime soon. Maybe it's an utopia and I should get win7 or 8. I was also looking for ReactOS but until now it is in alpha developpement and they just replicate xp
and they don't have fixed this yet. But We are far from all what I have dreamed: :-)

- My SP2 up to SP3 + all fixes
-All features nLite already offers
-Possibility to choose your own naming conventions or strategy
-A prompt that let you create or mount/assign folders to partitions
-user rights system like in linux or win7 (hips system also)
-a package or program manager that record all (registry entries, files, folders,...) created by a program during it's installation
-possibility to completely customize (icons set, windows themes...) but I guess this is possible with shell replacement LDE(x)...
-and so on.

I know I want a windows/linux fusion or openWindowsXP :rolleyes: . Just forget about this I am a perfectionist :whistle:

sorry I have no time to edit this post so it maybe not clear with typos.

Edited by frf954, 09 July 2012 - 09:59 PM.


#5
CharlotteTheHarlot

CharlotteTheHarlot

    MSFN Master

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,054 posts
  • OS:none specified
  • Country: Country Flag
After thinking about this some more, I suspect a plan of action will include the invention of a completely new global variable for WinXP (both for running XP and especially for setup) that would likely be called %ProfilesDirectory%. A few quick searches tell me that it does not already exist (someone please correct me!). This variable could be put to good use during setup once it is edited into the necessary setup files.

The next step could be replacing any non-variable hardcoded references to \Docume... and \Progra... and other derivatives with proper variables like %ProfilesDirectory% and %ProgramFiles%.

Of course this first demands a thorough audit (and complete expansion) of the WinXP setup files!

I can't promise when I can try this myself, I am not even sure which sources to use to cover all eventualities. But I have it generally outlined in my mind like this ...

- Take a spare computer and completely copy several representative Windows XP CDROMs
- Completely WinDIFF them, remove all duplicates, leaving one of every unique file.
- Expand every compressed file (*.in_ etc)
- Extract every Cabinet
- Search again and expand any further compressed files and/or further cabinets
- Repeat until all files are done.
- Brute force search every file for the target variables and strings
- Create a list of every file candidate for editing with its original state and location noted

... then post it up here and re-evaluate the merits of the project moving forward.

I cannot even guess right now if the number of files will be huge and unmanageable or not.

I hope that anyone else that has done anything along these lines offers their insight and tips :thumbup

... Let him who hath understanding reckon the Number Of The Beast ...


#6
frf954

frf954
  • Member
  • 8 posts
  • OS:XP Home
  • Country: Country Flag

After thinking about this some more, I suspect a plan of action will include the invention of a completely new global variable for WinXP (both for running XP and especially for setup) that would likely be called %ProfilesDirectory%. A few quick searches tell me that it does not already exist (someone please correct me!). This variable could be put to good use during setup once it is edited into the necessary setup files.

The next step could be replacing any non-variable hardcoded references to \Docume... and \Progra... and other derivatives with proper variables like %ProfilesDirectory% and %ProgramFiles%.

Of course this first demands a thorough audit (and complete expansion) of the WinXP setup files!

I can't promise when I can try this myself, I am not even sure which sources to use to cover all eventualities. But I have it generally outlined in my mind like this ...

- Take a spare computer and completely copy several representative Windows XP CDROMs
- Completely WinDIFF them, remove all duplicates, leaving one of every unique file.
- Expand every compressed file (*.in_ etc)
- Extract every Cabinet
- Search again and expand any further compressed files and/or further cabinets
- Repeat until all files are done.
- Brute force search every file for the target variables and strings
- Create a list of every file candidate for editing with its original state and location noted

... then post it up here and re-evaluate the merits of the project moving forward.

I cannot even guess right now if the number of files will be huge and unmanageable or not.

I hope that anyone else that has done anything along these lines offers their insight and tips :thumbup


I appreciate the effort , I still need to do now:

1 - move my pagefile to my P:\ partition ( done )
2 - move "Documents and Settings" to a partition
3 - move "Application Data" to T:\ partition
4 - move "Locals Settings" to T:\ partition
5 - rename the most folders I can.

I think I should proceed like this:

1 - search for all occurences of "Documents and Settings" , "Docum~1" , "Docume..." , "Application Data" , "Locals Settings", etc. in regseeker or other tool. ( done )
2 - export to .reg files what I have found. except for MRUs and similar stuff ( done )
3 - merge all .reg files into one big file for convenience.
4 - use find and replace of my TE to replace all occurences
5 - copy my "Documents and Settings" "Application Data" "Locals Settings" folders and content to selected patitions.
6 - rename all folder that can be renamed this way
7 - import the big .reg file

But I am afraid that this will screw up things, and I won't know until I tried. Someone already tried this and can tell us what happened?
Maybe I should do this from another user acount.

I have given up to change "Program Files" folder for my current installation I only focus on "Documents and Settings".

EDIT: There is also a method with 'symbolic links' but I am not sure I can rename folders.

Edited by frf954, 16 July 2012 - 03:53 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN