I am trying to reduce the size of my flash drive image to 2G.
I have 2 different Bart UBCD copies booting from the same 4G flash drive.
With the combined duplicate files it is to big to fit in 2G

Does anyone know of away to use UltraISO or another Util to Optimize (combine) the duplicate files on a flash drive to save space?

Thks

DSpyder

If the partition is formatted as NTFS you can use hardlinks allright.

This:
http://doubles.sourceforge.net/

could be handy.

There is no such thing as a "Bart UBCD", there is UBCD:
http://www.ultimatebootcd.com/
and UBCD4WIN:
http://www.ubcd4win.com/

If you mean two versions of UBCD4WIN, I would be curious to know why you need two copies.

In any case, how BIG are them, if two do not fit into 2 Gb they must be HUGE, and why should they fit in 2 Gb if you have a 4 gb stick?

jaclaz

Each copy of Bart is just over 1G and I also have a copy of Windows System recovery on the flash
1 copy boots without NTFS disk drivers and then unmounts those drive letters, so I have no NTFS Hard drives after it loads. That way the harddisk are more or less protected.
The other copy has all drives supported.

So the Flash needs to be fat or fat32 format to run with out NTFS drivers.

I have a handfull of 2g micro sd memorys that I would like to use and They can fit in a very small keychain usb reader.

I like to try new ways of doing things, doing the same thing gets old fast for me.

Thks 4 your fast reply.

You could move both builds into one iso, and use either mkisofs -duplicates-once or similar to save space.
You'd need to use a boot manager within the iso, and hack setupldr to replace "I386" with the second folder name.
It would also only save space on exposed files, not ones within an image / wim / sdi etc.

Hmm, the above, summed with the following:




makes me suggesting you a couple "crazy" thoughts.

1. what happens if you have in the BartPE ALL drive lettters already mapped in /DosDevices (or have a "fake", "full" migrate.inf)
2. would the MOUNTVOL /N (available since Server 2003) "effect" on Registry:
   http://social.technet.microsoft.com/Forums...69-68fbb788f129
   
   QUOTE
   According to the research, the function of both command line "mountvol /N" and "diskpart automount disable" is the same. They are the same thing.
   
   
   
   We can verify the status of Automatic mounting of new volumes by looking at the value of the following key:
   
   
   
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MountMgr\NoAutoMount
   
   
   
   If the value is set to 1: This indicates that Automatic mounting of new volumes is Disabled.
   
   
   
   If the value is set to 0: This indicates that Automatic mounting of new volumes is Enabled.
   
   work on BartPE (it should on Win2003 builds, but it may on XP ones)
3. Instead of disabling the Filesystem, disable the ATA/IDE and SATA BUSes

The second, IF working, appears to me as the "cleanest" solution.

jaclaz