Jump to content

[Release] Setup Source Changer


Siginet

Recommended Posts

I am working on a small exe that people can use in a Preinstallation Environment. They just run it... select the files to use to convert the setup source and then select the "*$~.LS" or "*$~.BT" folders they want updated. It also should work on any directory as well.

For use on a USB drive your source conversion files should have 2 folders in it. A "BT" folder and a "LS" folder... which obviouslly represents the "*$~.LS" and "*$~.BT" folders. Anything outside these folders will go to the root of your destination.

When it does the conversion it will create a folder inside of the destination called "CONVERT". Inside this folder it will create an "info.ini" file which will keep track of any changes made to the original destination. Plus any files which are overwritten are backed up in here as well.

I have actually successfully tested using it and it works very well. I even was able to convert my "Windows XP Pro Corp" into "Windows XP Media Center OEM"... Then to "Windows XP Pro Retail" and back to "Windows XP Pro OEM".

I also think it will be handy for things like Convert to use DriverPacks or not and so on...

Very Cool and Very handy for USB Setup users. :thumbup

I'll upload my test exe here soon. But beware it won't be pretty. lol. It does the job... but it will need a gui and a progress bar or something added to it.

=================================================

I have uploaded it here:

SetupSourceChanger v0.2

SetupSourceChanger.rar

Here is a tool to help gather the needed files from your sources by comparing 2 Windows Install sources.

ConversionFilesFinder v0.2

ConversionFilesFinder.rar

ReadMe.txt:

If you enjoy this tool please make a donation through paypal.com to chris@professorcpu.net

Or you can go here to make any donations:

http://support.siginetsoftware.com

Thanks,

Siginet

===========

How To Use:

===========

1. You will need to create your own source files for the conversion.

For instance any files that are different from one OS type to the next.

------------------------------------------------------------------------------------------

Here is a directory structure that I use that may work for you as well:

%Path%\SetupSourceChanger.exe

%Path%\XPHOME\OEM\BT\TXTSETUP.SIF

%Path%\XPHOME\OEM\BT\WINNT.SIF

%Path%\XPHOME\OEM\LS\I386\DPCDLL.DL_

%Path%\XPHOME\OEM\LS\I386\EULA.TXT

%Path%\XPHOME\OEM\LS\I386\OEMBIOS.BI_

%Path%\XPHOME\OEM\LS\I386\OEMBIOS.CA_

%Path%\XPHOME\OEM\LS\I386\OEMBIOS.DA_

%Path%\XPHOME\OEM\LS\I386\OEMBIOS.SI_

%Path%\XPHOME\OEM\LS\I386\PIDGEN.DLL

%Path%\XPHOME\OEM\LS\I386\SETUPP.INI

%Path%\XPHOME\OEM\LS\I386\SVCPACK.IN_

%Path%\XPHOME\OEM\LS\I386\winnt.sif

%Path%\XPHOME\RTL\BT\TXTSETUP.SIF

%Path%\XPHOME\RTL\BT\WINNT.SIF

%Path%\XPHOME\RTL\LS\I386\DPCDLL.DL_

%Path%\XPHOME\RTL\LS\I386\EULA.TXT

%Path%\XPHOME\RTL\LS\I386\OEMBIOS.BI_

%Path%\XPHOME\RTL\LS\I386\OEMBIOS.CA_

%Path%\XPHOME\RTL\LS\I386\OEMBIOS.DA_

%Path%\XPHOME\RTL\LS\I386\OEMBIOS.SI_

%Path%\XPHOME\RTL\LS\I386\PIDGEN.DLL

%Path%\XPHOME\RTL\LS\I386\SETUPP.INI

%Path%\XPHOME\RTL\LS\I386\SVCPACK.IN_

%Path%\XPHOME\RTL\LS\I386\winnt.sif

%Path%\XPHOME\UPG\BT\TXTSETUP.SIF

%Path%\XPHOME\UPG\BT\WINNT.SIF

%Path%\XPHOME\UPG\LS\I386\DPCDLL.DL_

%Path%\XPHOME\UPG\LS\I386\EULA.TXT

%Path%\XPHOME\UPG\LS\I386\OEMBIOS.BI_

%Path%\XPHOME\UPG\LS\I386\OEMBIOS.CA_

%Path%\XPHOME\UPG\LS\I386\OEMBIOS.DA_

%Path%\XPHOME\UPG\LS\I386\OEMBIOS.SI_

%Path%\XPHOME\UPG\LS\I386\PIDGEN.DLL

%Path%\XPHOME\UPG\LS\I386\SETUPP.INI

%Path%\XPHOME\UPG\LS\I386\SVCPACK.IN_

%Path%\XPHOME\UPG\LS\I386\winnt.sif

%Path%\XPPRO\OEM\BT\TXTSETUP.SIF

%Path%\XPPRO\OEM\BT\WINNT.SIF

%Path%\XPPRO\OEM\LS\I386\DPCDLL.DL_

%Path%\XPPRO\OEM\LS\I386\EULA.TXT

%Path%\XPPRO\OEM\LS\I386\OEMBIOS.BI_

%Path%\XPPRO\OEM\LS\I386\OEMBIOS.CA_

%Path%\XPPRO\OEM\LS\I386\OEMBIOS.DA_

%Path%\XPPRO\OEM\LS\I386\OEMBIOS.SI_

%Path%\XPPRO\OEM\LS\I386\PIDGEN.DLL

%Path%\XPPRO\OEM\LS\I386\SETUPP.INI

%Path%\XPPRO\OEM\LS\I386\SVCPACK.IN_

%Path%\XPPRO\OEM\LS\I386\winnt.sif

%Path%\XPPRO\RTL\BT\TXTSETUP.SIF

%Path%\XPPRO\RTL\BT\WINNT.SIF

%Path%\XPPRO\RTL\LS\I386\DPCDLL.DL_

%Path%\XPPRO\RTL\LS\I386\EULA.TXT

%Path%\XPPRO\RTL\LS\I386\OEMBIOS.BI_

%Path%\XPPRO\RTL\LS\I386\OEMBIOS.CA_

%Path%\XPPRO\RTL\LS\I386\OEMBIOS.DA_

%Path%\XPPRO\RTL\LS\I386\OEMBIOS.SI_

%Path%\XPPRO\RTL\LS\I386\PIDGEN.DLL

%Path%\XPPRO\RTL\LS\I386\SETUPP.INI

%Path%\XPPRO\RTL\LS\I386\SVCPACK.IN_

%Path%\XPPRO\RTL\LS\I386\winnt.sif

%Path%\XPPRO\UPG\BT\TXTSETUP.SIF

%Path%\XPPRO\UPG\BT\WINNT.SIF

%Path%\XPPRO\UPG\LS\I386\DPCDLL.DL_

%Path%\XPPRO\UPG\LS\I386\EULA.TXT

%Path%\XPPRO\UPG\LS\I386\OEMBIOS.BI_

%Path%\XPPRO\UPG\LS\I386\OEMBIOS.CA_

%Path%\XPPRO\UPG\LS\I386\OEMBIOS.DA_

%Path%\XPPRO\UPG\LS\I386\OEMBIOS.SI_

%Path%\XPPRO\UPG\LS\I386\PIDGEN.DLL

%Path%\XPPRO\UPG\LS\I386\SETUPP.INI

%Path%\XPPRO\UPG\LS\I386\SVCPACK.IN_

%Path%\XPPRO\UPG\LS\I386\winnt.sif

%Path%\XPPRO\VLK\BT\TXTSETUP.SIF

%Path%\XPPRO\VLK\BT\WINNT.SIF

%Path%\XPPRO\VLK\LS\I386\DPCDLL.DL_

%Path%\XPPRO\VLK\LS\I386\EULA.TXT

%Path%\XPPRO\VLK\LS\I386\OEMBIOS.BI_

%Path%\XPPRO\VLK\LS\I386\OEMBIOS.CA_

%Path%\XPPRO\VLK\LS\I386\OEMBIOS.DA_

%Path%\XPPRO\VLK\LS\I386\OEMBIOS.SI_

%Path%\XPPRO\VLK\LS\I386\PIDGEN.DLL

%Path%\XPPRO\VLK\LS\I386\SETUPP.INI

%Path%\XPPRO\VLK\LS\I386\SVCPACK.IN_

%Path%\XPPRO\VLK\LS\I386\winnt.sif

%Path%\XPMCE\OEM\BT\TXTSETUP.SIF

%Path%\XPMCE\OEM\BT\WINNT.SIF

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\BDATUNEPIA.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\BDATUNEPIA.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\DEBUGSVC.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\DOWN_GEM.PN_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\DOWN_OTTO.PN_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHCHSIME.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHCIR.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHCIR.IR_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHCIR.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHCIRCL.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHCIRFTY.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHCM.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHCM.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHCMFTY.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHCOMMON.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHCOMMON.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHDEBUG.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHDROP.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHENTT.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHEPG.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHEPG.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHEPGDAT.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHEPGDAT.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHEPGDATFTY.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHEPGDEC.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHEPGFTY.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHEPGNET.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHGLID.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHIEPG.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHIEPG.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHIEXTENS.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHIPLAY.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHIPLAY.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHIPLAYFTY.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHIPROXY.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHIPROXY.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHIPROXYFTY.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHITUNER.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHITUNER.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHITUNERFTY.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHIUSERXP.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHIUSERXP.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHIUSERXPFTY.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHIVIDCTL.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHIVIDCTL.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHIVIDCTLFTY.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHIWMP.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHIWMP.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHIWMPFTY.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHJPNIME.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHMSAS.EX_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHPLAYER.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHPROXY.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHREC.EX_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHRECOBJ.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHRECOBJ.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHRECOBJFTY.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHRES.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHRESCHS.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHRESDE.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHRESFR.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHRESJA.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHRESKO.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHSCHED.EX_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHSHELL.EX_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHSHELL.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHSHELLFTY.LD_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHSQDB20.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHSQQP20.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHSQSE20.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHTRAY.EX_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHUI.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\EHUIHLP.DL_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\GACUTIL.EX_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\GEMMAS~1.MC_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\MCDFTREG.IN_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\MCPREINS.EXE

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\MCSKIN.WM_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\MEDCTHLP.CAB

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\MEDCTRRO.EX_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\MEDIACTR.CAB

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\OTTO.MC_

%Path%\XPMCE\OEM\LS\cmpnents\MEDIACTR\I386\SNCHK.EX_

%Path%\XPMCE\OEM\LS\cmpnents\netfx\i386\netfx.cab

%Path%\XPMCE\OEM\LS\I386\ACCESSIB.CH_

%Path%\XPMCE\OEM\LS\I386\ACC_DIS.CH_

%Path%\XPMCE\OEM\LS\I386\binifix4.cmd

%Path%\XPMCE\OEM\LS\I386\EHOCGEN.DL_

%Path%\XPMCE\OEM\LS\I386\EULA.TXT

%Path%\XPMCE\OEM\LS\I386\IESUPP.CH_

%Path%\XPMCE\OEM\LS\I386\IEWEBHLP.CH_

%Path%\XPMCE\OEM\LS\I386\NETFX.CA_

%Path%\XPMCE\OEM\LS\I386\NETFXOCM.IN_

%Path%\XPMCE\OEM\LS\I386\OEMBIOS.BI_

%Path%\XPMCE\OEM\LS\I386\OEMBIOS.CA_

%Path%\XPMCE\OEM\LS\I386\OEMBIOS.DA_

%Path%\XPMCE\OEM\LS\I386\OEMBIOS.SI_

%Path%\XPMCE\OEM\LS\I386\PLUS.CA_

%Path%\XPMCE\OEM\LS\I386\PLUSOC.DL_

%Path%\XPMCE\OEM\LS\I386\PLUSOC.IN_

%Path%\XPMCE\OEM\LS\I386\presetup.cmd

%Path%\XPMCE\OEM\LS\I386\RegTweak.in_

%Path%\XPMCE\OEM\LS\I386\SETUP.INF

%Path%\XPMCE\OEM\LS\I386\SETUPP.INI

%Path%\XPMCE\OEM\LS\I386\SONIC.CA_

%Path%\XPMCE\OEM\LS\I386\SONIC.IN_

%Path%\XPMCE\OEM\LS\I386\SUPP_ED.CH_

%Path%\XPMCE\OEM\LS\I386\TXTSETUP.SIF

%Path%\XPMCE\OEM\LS\I386\undoren.cmd

%Path%\XPMCE\OEM\LS\I386\wbemoc.in_

%Path%\XPMCE\OEM\LS\I386\winnt.sif

%Path%\XPMCE\OEM\LS\I386\WMP10.CH_

%Path%\XPMCE\OEM\LS\I386\WMPERR10.CH_

%Path%\XPMCE\OEM\LS\I386\WPA.INF

%Path%\XPMCE\OEM\LS\I386\WPDTRACE.DL_

------------------------------------------------------------------------------------------

2. Now... what I do is create my USB drive with:

Windows XP Pro OEM

Then I move the entire contents of the usb drive into a folder called "XPPO".

Then I create the usb drive with (Do not format):

Windows XP Pro Corp

Then I move the entire contents of the usb drive into a folder called "XPPC".

Now I use my other tool ConvertionFilesFinder.exe to compare the differences.

It will grab all of the needed files into a directory called "NewFiles" for me.

Any "$WIN_*$.~LS" / $WIN_*$.~BT" folders in my "NewFiles" directory I rename to "LS" / "BT".

I can keep or delete the "NewFiles\info.ini" file created by ConvertionFilesFinder.exe.

I rename the "NewFiles" folder to whatever I want and keep that for use with SetupSourceChanger.exe

For instance I can Rename "NewFiles" to "Corp" and place it in "CONVERT\XPPRO\CORP" to organize things.

3. Whenever I want to change my XP Pro OEM to Corp...

I just execute SetupSourceChanger.exe

Select my "CONVERT\XPPRO\CORP" directory as the source.

Then I select my "$WIN_*$.~LS" directory on the root of my usb drive as the destination.

It will then convert XP Pro OEM into Corp.

For instance I can point to my "CONVERT\XPMCE\OEM" directory as the source

and then my "$WIN_00$.~LS" as the destination and it will change it

into Media Center Edition.

==========================================================================================

This is a simple beta release. So you can expect me to improve on it if need be.

Please make sure you backup your files!

Give me your thoughts and feedback in this thread:

http://www.msfn.org/board/index.php?showtopic=129049

Enjoy!

Edited by Siginet
Link to comment
Share on other sites


Very nice and interesting :)

I think that the SetupSourceChanger will be very handy for people

who often need or want to Install different types of XP from USB-stick.

Unfortunately, I cannot do a real test of the SetupSourceChanger

for Install of XP from USB, because I don't have all these different types of XP.

However, a test simulating the process would be possible. ;)

What is the reason for Upating in case of Windows XP Media Center OEM

the files binifix4.cmd - presetup.cmd and undoren.cmd

which are files NOT belonging originally to XP ?

Edited by wimb
Link to comment
Share on other sites

Very nice and interesting :)

I think that the SetupSourceChanger will be very handy for people

who often need or want to Install different types of XP from USB-stick.

Unfortunately, I cannot do a real test of the SetupSourceChanger

for Install of XP from USB, because I don't have all these different types of XP.

However, a test simulating the process would be possible. ;)

What is the reason for Upating in case of Windows XP Media Center OEM

the files binifix4.cmd - presetup.cmd and undoren.cmd

which are files NOT belonging originally to XP ?

Those are files needed in my setups to be correct. ;) I beleive those files are created by the Install From USB Gui when it creates the usb files? They are not needed on media center as well? In my example.. i also use driverpacks. Some of the files I have listed do not have to be put in everyones list of files. Most of them yes... but not all of them. Basically it is best for anyone wishing to do this to use a program like Beyond Compare to compare the differences in their files.

Link to comment
Share on other sites

The BT and LS folders are only needed for USB stick installs. If you use The "Install From USB" utility in this forum you will notice it makes 2 folders. The "*BT" and the "*LS". The "LS" directory is basically the windows install disk itself. Whereas the "BT" directory are the Boot files for setup. Like when you start an installation of windows xp from within windows. It dumps files on your hard drive that are needed for the install. This is the exact same thing. ;) Or when you create a multiboot disk with XP PowerPacker. It creates a boot folder which is the same as the "BT" directory. ;)

Link to comment
Share on other sites

The BT and LS folders are only needed for USB stick installs.

More generally the two directories are created also when installing windows through WINNT.EXE and WINNT32.EXE.

And they are also used on the now becoming historical "multiboot CD/DVD" guide :thumbup :

http://flyakite.msfn.org/

The names are hardcoded by the good MS guys, and while BT is obviously short for "BooT files", LS origin is unknown AFAICR. :unsure:

@siginet

@wimb

You both may want to look at the newish two features of grub4dos:

dd


******************************************************************************
*** New command 'dd' to copy files ***
******************************************************************************

Usage:

dd if=IF of=OF [bs=BS] [count=C] [skip=IN] [seek=OUT]

Copy file IF to OF. BS is blocksize in bytes, default to 512. C is blocks to
copy, default is total blocks in IF. IN specifies number of blocks to skip
when read, default is 0. OUT specifies number of blocks to skip when write,
default is 0. Skipped blocks are not touched. Both IF and OF must exist.

Both IF and OF must have a leading device name, i.e., of the form `(...)'.
You may use `()' for the current root device.

dd can neither enlarge nor reduce the size of OF, the leftover tail of IF
will be discarded. OF cannot be a gzipped file. If IF is a gzipped file,
it will be decompressed automatically when copying.

dd is dangerous, use at your own risk. To be on the safe side, you should
only use dd to write a file in memory.

In some cases when writing a file in NTFS, dd might fail.

If you attempt to write a file that is not in memory by starting dd in a menu,
you will safely be refused :-)

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~!!!!
!!!! Caution! Both IF and OF can be a device name which stands for !!!!
!!!! all the sectors on the device. Take utmost care! !!!!
!!!!______________________________________________________________________!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

and

write


******************************************************************************
*** Use 'write' to write a string into a device or file ***
******************************************************************************

Usage:

write [--offset=SKIP] ADDR_OR_FILE INTEGER_OR_STRING

SKIP is an integer and defaults to 0.

If ADDR_OR_FILE is an integer, then it is treated as a memory address, and
INTEGER_OR_STRING must be an integer value. The integer INTEGER_OR_STRING
will be written to address (ADDR_OR_FILE + SKIP).

If ADDR_OR_FILE is a device or a file, then INTEGER_OR_STRING is treated as
a string which will be written to ADDR_OR_FILE at offset SKIP (in bytes).

The string is quoted with nothing, that is, neither with the single quote
char(') nor with the double quote char(").

Space char must be quoted with back slash(\).

Single quote char(') and double quote char(") are not interpreted specially
and can be used directly in the string.

Some C-style quote sequences are interpreted as follows:

\NNN character with octal value NNN (1 to 3 digits)

\\ backslash

\a alert (BEL)

\b backspace

\f form feed

\n new line

\r carriage return

\t horizontal tab

\v vertical tab

\xHH byte with hexadecimal value HH (1 to 2 digits)

Just like dd, the write can neither enlarge nor reduce the size of the
destination file, the leftover tail of the string will be discarded.
The destination file cannot be a gzipped file.

Again like dd, the write command is also dangerous, use at your own risk.
And to be on the safe side, you should only write to memory files.

In some cases when writing a file in NTFS, the write might fail.

If you attempt to write a file that is not in memory by using write in a menu,
you will safely be refused :-)


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~!!!!
!!!! Caution! The file to write can be a device name which stands !!!!
!!!! for all the sectors on the device. Take utmost care! !!!!
!!!!______________________________________________________________________!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


Still experimental, NOT recommended for "production" right now, but worth some time considering. :)

@wimb

Additionally, check the new uuid:


******************************************************************************
*** New command 'uuid' to identify partitions ***
******************************************************************************

Usage:

uuid [DEVICE] [UUID]

If DEVICE is not specified, search for filesystem with UUID in all partitions
and set the partition containing the filesystem as new root (if UUID is
specified), or just list uuid's of all filesystems on all devices (if UUID is
not specified). If DEVICE is specified, return true or false according to
whether or not the DEVICE matches the specified UUID (if UUID is specified),
or just list the uuid of DEVICE (if UUID is not specified).

Example 1:

find --set-root uuid () 7f95820f-5e33-4e6c-8f50-0760bf06d79c

which will find a partition with uuid=7f95820f-5e33-4e6c-8f50-0760bf06d79c
and set the partition as root if found.

Example 2:

uuid ()

which will print the uuid of the current root device.

That could be useful to "identify" the stick without the need of a "tag" file. ;)

@siginet

GOOD work! :thumbup

jaclaz

Edited by jaclaz
Link to comment
Share on other sites

@jaclaz

Thanks for the interesting Info on new features of grub4dos. :)

Instead of having your XP Setup Source on CD, by using winnt32.exe you will

make the $WIN_NT$.~LS folder on your Local Harddisk containing the XP Setup Source files.

This making of a so called Local Source will be the explanation for the naming of the LS Folder. ;)

Edited by wimb
Link to comment
Share on other sites

I have an update comming really soon. I went ahead and threw together a simple gui. I also made another gui to help in the gathering of files to use for conversion. :)

Just as a note. This tool does not have to be used for only usb installs. It can also be used when you are integrating files with the RVM Integrator. If you are like me and create multiboot disks with each different type of windows on it this will come in handy as well. You can easily integrate XP Pro OEM... then copy the contents to a new directory and convert it to Retail... then do the same thing and convert it to corp and so on. Which will save time.

Thanks for that new info as well Jaclaz! That is actually exactly what I was hoping for when I first mentioned converting the source files.

I am very new to Grub4Dos so I will probably need some help on how to write the commands for it.

Thanks a lot! :thumbup

BT=BOOT

LS=Local Source

Now that makes a lot of since. ;)

Edited by Siginet
Link to comment
Share on other sites

You guys are free to incorporate this into your tools as well. Let me know if you need any changes. ;)

Hi Siginet,

Thanks for Sharing this with us :)

The ConversionFilesFinder and SetupSourceChanger are very handy Tools. :yes:

I will add them to U_XP_SET package.

Thanks again,

wimb

Link to comment
Share on other sites

  • 3 weeks later...

In the next version of SetupSourceChanger I will be implementing an option to choose wether or not to convert the files back to default before adding the files (Which is what it does autamatically now) or you will be able to add changes without converting to default.

What I mean is this...

Lets say you want to convert Win XP Pro OEM Without Driverpacks to Win XP Pro VLK With DriverPacks.

In the current version you would have to have a conversion folder with all of the files for VLK and Driverpacks.

But in the next version you can have seperate conversion folders which you can add incrementally.

Convert OEM to VLK... then Convert the VLK to VLK with Driverpacks. ;)

Then whenever you want to go back to the default of Win XP Pro Without DriverPacks you just select an empty conversion folder and tell it to go back to default. :D

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...