Markymoo

Thats why i mentioned dont put in anywhere else other than boot and root.

is that why u getting problems coz u r using memdisk??

A lesson learnt. Don't use betas unless absolutely necessary. I am using 2.0.11 ultimatebootcd has the sense to use cdshell now. You can always take a look and use my cdshell script it runs 27 operating systems plus utils. http://www.911cd.net/forums/index.php?act=...st=0#entry37238 2k3 Enterprise,DataCenter,Std,Web 2k Advanced Server,Datacenter,Server,Workstation XP Tablet,MediaCenter,Std,Home,nLite,oem,custom NT4 Enterprise,Server,Workstation Linux Knoppix Ultimatebootcd Erd Commander Acronis Utils ME, 98, 95 Norton Av BartPE Ghost

I've checked xpcreate installation 2x and all updates are correct size. After nLite reducing i get the same three updates needed in windows update as Nemesis300. 835732 828026 826939 (Rollup) I install the three updates and reboot and windows update still tells me i need those three updates again reboot again..... I try with sp2 I removed all apart from experimental and winnt32 text support.

I did it different. I just extracted my images dir from ultimatebootcd to my AIO and then loaded the images individually. Saves some space.

Yes FBi_ moving the isoinux folder to root cures the loading of knoppix boot screen while booting another os. I thought i tried this already and it failed. I was messing around with isolinux.bin at the time. I was trying to hexedit isolinux.bin so i could have isolinux in the knoppix folder but isolinux.bin checks itself for modification and results in checksum error. Trying too hard i guess. I update the mini-guide to reflect this. Well Done FBi_! You did good

Exactly what i was saying Hista but not for quite a time or at all. Regtweaks are low priority at moment. We shall see. EDIT: I will convert all the regs to inf's.

I will tell you whats wrong with it the line below. if $lastKey == key[3]; bcdw /boot/isolinux/isolinux.bin Its treated as two seperate commands, it will always boot linux whatever you press from this line onwards unconditionally. You have missed a then statement. It should be if $lastKey == key[3]; then bcdw /boot/isolinux/isolinux.bin Now it will work fine. This line if $lastKey == key[2]; then memdisk /98SE.IMA is fine as long as you have 98SE.IMA in the root dir which i'm sure you have. I suggest you download a 98SE.IMA again from here

This is whats on my xp part of AIO multi-boot now. "Standard Attended" "Media Center" "Tablet Pc" "Home Edition" " Std Unattended Auto Partition" " Std Unattended Manual Partition" " Std Unattended Auto Partition OEM" " Std Unattended Manual Partition OEM" "nLite Unattended Auto Partition" "nLite Unattended Manual Partition" "nLite Unattended Auto Partition OEM" "nLite Unattended Manual Partition OEM"

Use nLite and rip it out from the heart.

You probably have this Blaster Worm Removal Tool for Windows XP and Windows 2000 (KB833330) which you should replace with this go here or one of these Go here for mydoom patch Blaster/Nachi Worm Blaster/Nachi Worm

You can make a dos bat file that will run winnt32.exe from your cd. This will force it to install/setup to that location. You can also specify your answer file on the command line too. This will be automated. This will create an install on D: Change this to your requirements. The CD is the source where your setup files are coming from in this case E: Make a dos batch file. and include the below. E:\I386\winnt32.exe /syspart:D: /tempdrive:D: /unattend:E:\I386\winnt.sif /s:E:\I386

That is not a hotfix that is a sasser removal tool you need to replace it with the patch to stop getting it in the first place go here

You only need winnt.sif in the boot folders not i386. Delete all sifs from i386 folders that goes for txtsetup.sif too. Changing repartition to yes does it autoformat? If not you know your winnt.sif is being ignored and corrupt so recreate using xp deployment tools.

all you have to do is copy bcdw.csm into your cdshell modules folder.

@ nuhi Its great to see your injected enthusiasm in such a needed tool making waves and benefiting the majority. It just gets better and better where will it all end....Right now i can't see an end. So many possibilties. This is getting huge. We all passengers on a race track and nuhi the driver. Turn my back..Bang! here comes another beta release.

Yes it takes effort just like yourself[deXter] have put in the effort and look at the rewards,benefits. Whatever it is its better than this tangled mess. Making a start now is good. If we start setting standards everything will fall into place. Our wishes could all be put on one main website but we can do all from here. Look at Kelly's corner its not all .reg files but .vbs too. Setting the standard from the beginning is the key. How tedious is it to look through a big list to find a tweak. Better to have attachments. This is one idea. We have 2 threads+..... One with a tested approved reg file with all the tweaks in one file to download. This can include great essential common tweaks everybody needs. Then below that we have the listings of each individual reg tweak for that file so people can just grab cetain ones. All of these have been tested and moderated and updated from the experimental thread i discuss now. We then have another thread thats experimental where all tweaks get tested. Members can post there tweaks here definately not giant lists and not tweaks that are already tested better as a attachment so posts are reduced. We just have reg tweaks nothing else. If people want to post there comments they do it in another thread. Consider the amount of time people come here to look for a tweak and then times that by how many pages they look at thats alot of hours wasted. We can also have a thread for not so demanding tweaks off the wall freaks(tweaks). Yes theres thousands of tweak monitor registry etc. but 80% want the same tweak either turned on or off. Theres a set number that all want. we can have an ie thread, an office thread. how far do we go...? We can list all the explorer settings in 1 thread all the ie in another as these are big reg exports but include lots of tweaks. There are a thread to themselves. @[deXter] Thinking the same. Your list for one is covering alot already. Looking through the threads there can't be much more left to get. Alot being duplicated 10x. Theres only so many nt services etc. Get this going well then we can worry about software later. Heres a program im using at the minute its Active Registry Monitor takes 2 snapshots of the registry a before and after and compares them. Dosen't take long to find your needed tweak setting in the registry. p.s. apologies theres no reg tweaks in this post but i don't think i can make it worse.

I seen a few claiming to be ultimate tweak files but they havent got simple ones like set the ie homepage. Why dont we all keep to one standard and agree and make a all time ultimate reg file we all use with every single tweak going and then comment out what we dont want for ourselves. I've seen three registry tweaks to do the same thing but only one works. We apply this ultimate reg file as a Sticky Thread for all to see and any tweaks that want to be added to it have to be tested and approved so we know there working. It takes several seconds to test a reg file and to know if its working or not. AND Someone writes a program with a database of tweaks that can be added to and so no duplicate tweaks can be added. If this is moderated before you know it we have a big working tested database of tweaks. In the program you select the tweaks you would like and then it exports your chosen tweaks to a reg file for you. We need to get our heads together and do this. Count me in. Edit .nfo files with notepad [HKEY_CLASSES_ROOT\.nfo] @="txtfile" "PerceivedType"="text" "Content Type"="text/plain" [HKEY_CLASSES_ROOT\.nfo\PersistentHandler] @="{5e941d80-bf96-11cd-b579-08002b30bfeb}" [HKEY_CLASSES_ROOT\.nfo\ShellNew] "NullFile"="" Whats the point of compiling if they dont work. taken from [deXter] ultimate tweak list ;Remove Shared Documents from My Computer [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\MyComputer\NameSpace\DelegateFolders\{59031a47-3f72-44a7-89c5-5595fe6b30ee}] but this one does work from another source. ;Remove Shared Documents from My Computer [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer] "NoSharedDocuments"=dword:00000001

Its confusion thats why i put here and keeping the same name is less confusion.

Nothing wrong with that Try removing total commander that has long filename problems.

Ah well you said nothing about BartPe. Guess what my AIO has BartPE too. I run BartPE put every program plugin going. No problem at all Rename the BartPe I386 folder to BART Make a BART.DAT boot file Hexedit BART.DAT change I386 to BART Edit setupldr.bin in BART folder and change I386 to BART copy winbom.ini to root Run BART.DAT from a script Never got the error you described as long as i use -j1 You could try a utility such as this to see which programs are using long filenames. And sacrifice the offending program. Also check your drive for errors. Extra long filename is supported with the ISO9660:1999 and UDF filesystems.

Yes its working with msdosinitiated="0" Nice One You know what?.... "I have been nLited" Yes i didnt study straight away, happy it was working for awhile. I meant to say Copy the file smss.exe in your nLite XP I386\system32\ folder to your boot\system32\ folder. this and the language problem is sorted!!

@Nuhi I have removed OriSrc="C:\XP" look up I described all that in the solution. The PRO1 is the boot folder C:\$WIN_NT$.~BT renamed.

Temporary Working Solution to put nLite on Multi-Boot AIO. Do not remove winnt32.exe support in the components list in nLite or you will come stuck. Move your reduced nLite xp folder into your AIO folder. Using the gosh method slimming down technique(will not make xp any smaller but have to do to make the boot folder). Run "winnt32 /noreboot" from your nLite I386 folder. Rename C:\$WIN_NT$.~BT to ... lets call it PRO1 for clarity and move it to your AIO folder. You probably already have a PRO1 folder so call it 4 digits whatever. Delete BOOTSEC.DAT and migrate.inf in PRO1 folder. Delete C:\$WIN_NT$.~LS Copy the file smss.exe in your nLite XP I386\system32\ folder to your PRO1\system32\ folder. Thats right its missing. Edit your txtsetup.sif setupldr.bin in PRO1 folder as usual and lastly winnt.sif which i explain below. Using gosh method with nLite makes the below winnt.sif in C:\$WIN_NT$.~BT which is now your PRO1 folder. This dosent work. I've pasted it here to remedy quicker. So use your own or the one i've included which i pasted straight after. nLite winnt.sif This is not working. I dont know why just yet. [data] msdosinitiated="1" floppyless="1" AutoPartition="1" UseSignatures="yes" InstallDir="\WINDOWS" EulaComplete="1" winntupgrade="no" win9xupgrade="no" Win32Ver="a280105" uniqueid="C:\WIN\IGB" OriTyp="3" [regionalsettings] Language=00000809 LanguageGroup=1 [userdata] productid="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX" productkey="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX" [OobeProxy] Enable=1 Proxy_Bypass="127.0.0.1" Flags=9 Autodiscovery_Flag=0 Use the one below or your own instead [Data] AutoPartition=1 MsDosInitiated="0" UnattendedInstall="Yes" [unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=Yes Repartition=Yes TargetPath=\WINDOWS FileSystem=* UnattendSwitch="yes" WaitForReboot="No" DriverSigningPolicy=Ignore KeyboardLayout="United Kingdom" [GuiUnattended] AdminPassword=* EncryptedAdminPassword=No OEMSkipRegional=1 TimeZone=85 OemSkipWelcome=1 [userData] productid="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX" productkey="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX" FullName="nLite Rules" OrgName="I have been nLited" ComputerName=COMP [Display] BitsPerPel=32 Xresolution=768 YResolution=1024 Vrefresh=85 [TapiLocation] CountryCode=44 Dialing=Tone AreaCode=071 [RegionalSettings] LanguageGroup=1 Language=00000809 [identification] JoinWorkgroup=HOME [Networking] InstallDefaultComponents=Yes [branding] [Components] [shell] [GuiRunOnce]

Ok first up make sure you have plenty of space on your hard drive because cdimage demands alot if the image is big. If you get hangs or cdimage quitting this is usually from not enough space. @ArmyDoc yes cdimage will let you create an iso/joliet iso @Phil you need to add the -j1 switch. It does work! Here is my command line this should help cdimage.exe -l"ALLWINDOWS" -t08/23/2001,09:00:00 -h -j1 -b"C:\AIO\BOOT\loader.bin" -o -m "C:\AIO" "C:\AIO.iso" Failing that download cdimageGUI HERE