Rudi1 Posted May 22, 2004 Posted May 22, 2004 @ZuluDC, OO YEAH...finally good news, now just to fix home edition problem and i'm on the road again.this is really great news,so now nlite can work with every version
nuhi Posted May 22, 2004 Author Posted May 22, 2004 beta 8.4 is out.- fixed manual installation (temporary fix by Markymoo)- fixed missing txtsetup entry for help and tour (home edition bug and maybe some others)- moved Distributed Transaction Coordinator to Experimentaledit: o yes, and big thanx to Markymoo for his manual install helpIf you are building AIO cd then after gosh slim you got session_3 error see below.
bonedaddy Posted May 22, 2004 Posted May 22, 2004 nuhishould I try 8.4 or wait, the 16 bit problem?previous ver not workingbonedaddyEDITwill do, I'll being watching
nuhi Posted May 22, 2004 Author Posted May 22, 2004 @bonedaddy, i still haven't got time to look into 16-bit problem, i will put it in changelog if it becomes fixed
Markymoo Posted May 22, 2004 Posted May 22, 2004 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$.~LSCopy 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=00000809LanguageGroup=1[userdata]productid="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"productkey="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"[OobeProxy]Enable=1Proxy_Bypass="127.0.0.1"Flags=9Autodiscovery_Flag=0Use the one below or your own instead[Data]AutoPartition=1MsDosInitiated="0"UnattendedInstall="Yes"[unattended]UnattendMode=FullUnattendedOemSkipEula=YesOemPreinstall=YesRepartition=YesTargetPath=\WINDOWSFileSystem=*UnattendSwitch="yes"WaitForReboot="No"DriverSigningPolicy=IgnoreKeyboardLayout="United Kingdom"[GuiUnattended]AdminPassword=*EncryptedAdminPassword=NoOEMSkipRegional=1TimeZone=85OemSkipWelcome=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=32Xresolution=768YResolution=1024Vrefresh=85[TapiLocation]CountryCode=44Dialing=ToneAreaCode=071[RegionalSettings]LanguageGroup=1Language=00000809[identification]JoinWorkgroup=HOME[Networking]InstallDefaultComponents=Yes[branding][Components][shell][GuiRunOnce]
AztecMystic Posted May 22, 2004 Posted May 22, 2004 A little tribute Even if I'm just starting this windows unnatended stuff, I just love this tool (it's in the lower section hehe)
nuhi Posted May 22, 2004 Author Posted May 22, 2004 @Markymoo, thank you, thank youI just tried your fix and it works, but i needed to copy smss.exe from original i386\System32\smss.exe to BOOT\system32\smss.exe and i386\system32\smss.exeWinnt.sif i used from nlite...edit:@AztecMystic, @Markymoo, yes, you are right, only in BOOT\SYSTEM32\smss.exe
Markymoo Posted May 22, 2004 Posted May 22, 2004 @Nuhi I have removed OriSrc="C:\XP" look upI just tried your fix and it works, but i needed to copy smss.exe from original i386\System32\smss.exe to BOOT\system32\smss.exe and i386\system32\smss.exeI described all that in the solution. The PRO1 is the boot folder C:\$WIN_NT$.~BT renamed.Copy the file smss.exe in your nLite XP I386\system32\ folder to your PRO1 folder. Thats right its missing.
nuhi Posted May 22, 2004 Author Posted May 22, 2004 @Markymoo, thanks to your help it's little simpler.You are right, only copy smss.exe to BOOT\SYSTEM32\SMSS.EXE (or PRO1)but....that winnt sif you mentioned, it's not nlite generated, it's windows..only error is msdosinitiated="1"needs to be changed to msdosinitiated="0" and it works...no temporary files errorTest it and if i'm mistaken correct me, i'm going now to find a source of the problem.
Markymoo Posted May 22, 2004 Posted May 22, 2004 Yes its working with msdosinitiated="0"Nice OneYou 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 Posted May 22, 2004 Author Posted May 22, 2004 @Markymoo, You know what?.... "I have been nLited"hehe, good one...have you seen one with a vacuum cleaner or what Just to let you know i sorted half of the bug...whell the more important half.There is no need of copying smss.exe anymore...it was usetup.exe error...it gets renamed to smss.exe during setup...grrr i missed thatnow only thing you need to do is to change msdosinitiated="1" to msdosinitiated="0" if needed.beta 8.5 uploaded, nothing new except that big issueI think now the bugs are reduced to good number...maybe it's time to continue REDUCING
kalavera Posted May 22, 2004 Posted May 22, 2004 I have found a strange thing ... and i'm asking if someone else has this problem too :When i use nLite to remove components from the xp cd, after making the iso, when i test it on VirtualPC 2004, in the text setup copying files stage it takes a lot of time, and in some files it appears to stop and then continues but during that time there isn't disk activity.It appears that the setup is always taking the exact time to copy files, even if they aren't in there!I say this because if i don't use nLite and create the same customized windows xp iso (without the components removed), the file copying is constant and there is always disk activity.Anyone else can test this?nuhi: Good work with this new version and the nice UI.Do you have in your todo list the readonly and uppercase problem?Keep the good workThanks
nuhi Posted May 22, 2004 Author Posted May 22, 2004 @kalavera, weeeird, mine installation is way faster...try it on real pc, i don't knowI'm using vmware and it's faster there too.Do you have in your todo list the readonly and uppercase problem?Both sorted out...see the changelog on the first page.
kalavera Posted May 22, 2004 Posted May 22, 2004 Thanks for the quick reply ... i will try it with vmware and then in real pc ... i will back with report.Bye
Jazz Posted May 23, 2004 Posted May 23, 2004 I have found a strange thing ... and i'm asking if someone else has this problem too :When i use nLite to remove components from the xp cd, after making the iso, when i test it on VirtualPC 2004, in the text setup copying files stage it takes a lot of time, and in some files it appears to stop and then continues but during that time there isn't disk activity.It appears that the setup is always taking the exact time to copy files, even if they aren't in there!I say this because if i don't use nLite and create the same customized windows xp iso (without the components removed), the file copying is constant and there is always disk activity.Anyone else can test this?nuhi: Good work with this new version and the nice UI.Do you have in your todo list the readonly and uppercase problem?Keep the good workThanksExactly, i got the same problem... some of the files are usrvoica.(something) and usr(somethingss) i'll get u the exact file name if u want.. Its nit that they give an error or something.. but the copy process takes a lot longer on these files.. dunno why ?and ya i've even tried that on a real pc so i know for real the bug is persistent.. but its not a priority now.. so it can wait BYe,Jazz
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now