[wherzdaluv]

now there is so much knowlege on this site to try and cram it is overwhelming. i have used nlite to make a set of xp's from xp_no sp's >thru sp2 now sure the combined total is over 700 MB standard cdr, why not buy a 12X dvdR all i can say is why waste my money when they have already made an over 52X just raking in the money at 12X.

i have a versions a,b,c,d:--> a=before SP b=only sp1 no hotfixed , c=sp1 with hotfixes, d=sp2

now nLited these down to a total of 932MB

so i was cutting the 4 in 1/2 to> A, B then C, D which would make it on a CDR 700MB

i cannot use gosh's slimming xp because nLite will not work with it, sure i can copy dotnet to it, just dont have the knowlege to keep it from trying to copy things that are no longer there.

Removed by Alanoll

so to the point of this post is basically this

creating an AIO cd of ONLY winXP>>notice the "ONLY" part, dont care about 95,98,me, homexp

cd shell doesnt have very simple help understandable files, is there not a way when an OS xpA->xpD use alot of the same files , so creating a boot file that says oh need font Times Roman Numeral, and it just says"Oh thats over here on this area of my disk" and go get it, so when an update happens to Times Roman Numeral, we dont need version 1 thru 1000, just have version 1000, and that was simple explanation i could explain, when xp came out, they had a printer.driver yet last xp has a printer driver which has all drivers from xpA drivers. why do i need to have that on the disk and not just if i decide to make a partition with only sp1 yet get the drivers from sp2 version of xp.

so in earlier statement where i have 4 versions ripped at 900+ MB when knowing that there is plenty of the same used from 1->4, how do i make or find a program that researches to say this folder of I386 has the same and more, why keep I386A when I386D has I386A---i386C and new updates I386D. it would be on the same CDR, just why refer to that old i386A when i386D has that and more.

where i would be able to create the original versions a,b,c,d of the originals using alot of the same which is over 2 gig, yet say DRIVER.CAB from "xp before SP" to recognize DRIVER.CAB "at which ever version they are at" to save 29,000kb for each version.

i dont know if what i said made any sense, and i wont be back at the computer for about a week 02/23/05, but will love all info and simple understanding how to make 4 different i386's recognize each other and dump the old one before burning.

thanks

wherzdaluv

This post has been edited by Alanoll: 24 February 2005 - 09:45 AM

[jaclaz]

There are some programs that will make an "optimized" ISO image, basically, if the same file is present into two or more places, only one instance will be written on the CDFS filesystem image, all the others will be just pointers to the one file.

then search on the board for examples of usage of mkisofs or cdrecord

You need a version that allows the " -duplicates-once" switch, like the one within BartPE (Reanimatolog version).

Here is a GUI for it:
http://members.chell...100/The_GUI.htm

There is also the Cdimage program from Microsoft, but it is "for internal use only".

jaclaz

[Alanoll]

@wherzdaluv

Quote

1. This is not a warez site! Links/Requests to warez and/or illegal material (porn, cracks, serials, etc..) will not be tolerated. Discussion of circumventing activation/timebombs/keygens or any other illegal activity will also not be tolerated. If you ignore any of the aforementioned you will receive a final warning. If you choose to continue, you will be banned without notice.

Careful Careful with that link i removed...

also...
http://flyakite.msfnhosting.com