tester_pedro

2 LeveL: cause you were so lazy i did it for you. i went to microsoft.com to their knowledge base and searched for these information abou the hotfixies. 75% of these hotfixies add new files, that weren't in the original. a lot of files. so in my point of view it is possible that it is "growing".

and without integrate ^ this? EDIT: it is possible to make x64 on 32bit sys and vista on xp?

I would do this: MB: is ok what you choosen OS: Vista Ultimate x64 >> why not? you have vista ready hw, lot of problems running XP RAM: 8GB >> Ultimate PCs have minimum of 4GB GPU: nV9800 x2 >> enough cause games today are crap anyway CPU: C2Q (2.4Ghz would be enough but no limit with this), C2E (extreme is extreme for "nothing" - in my POV) >> there will be not much app where all cores will run 99% PSU: 600W with 80+ efficiency >> enough, i would never go into SLi,3-Way SLi or anything like that, i like mother nature HDD:2xSATA disks in RAID0 (if you want ultimate go for 2xSSD SLC ) DVD: why not BluRay? PPU: none Case: your choice Key&Mouse: your choice LCD: viewsonic, dell 24"+ >> nothing less best would be to buy a normal PC and x360 for games, cause developers these days do crap not games, console gaming is better investment in the future

"quickreply":vlite mounts install.wim from vista dvd, deletes some files you choose, changes files that works like catalogs, that tell the installer what to install. that's it. try to download waik (windows automated installation kit > hope it is right ) from microsoft and look for tools imagex and peimg. I played with it only a bit, but it is easy, so test it yourself.

Thanks man. I thought that it can be done directly but after many unsuccessfully tries giving it up and will try the Bootfolder tool and some info from Gosh's guide. Will give some info how it ends.

looked (maybe I should say sniffed) over many forums about multiboot themes and find nothing that could help me. maybe if I edit txtsetup.sif and this: SetupSourcePath = "\" ??? give it a try.will inform about the progress... EDIT1: got it WORKING!!! not fully but it looks its on a good way. What I did? w2sect.dat duplicate,hexed txtsetup.sif path change setupldr.bin hexed removed my winnt.sif (eula skip,productkey) Now no fatal error message popup but it ask for the path of different files till the T-37 (Device instllation). My question in this stage: my winnt.sif was: [userData] ProductKey=XXXXXX [unattended] OemSkipEula=Yes is it ok that it looks like that? I mean is the switch UnattendMode= or UnattendedInstall = not needed? Thanx for hints. EDIT2: after hundreds of making the iso over and over again I have put this in winnt.sif too: [Data] MsDosInitiated=0 this 2 lines should avoid the fatal error mentioned in first post. BUT STILL IT ASKS ME FOR THE PATH FOR FILES (starts with ASMS,NT5*.CAT...) Please help!!! I really need some help.

actually this tool is not what I'm looking for ,it makes the same as winnt32 /noreboot command am I right? no need for that... but THANX

thanks for answer... yes I know gosh's guide but don't like the idea with winnt32 /noreboot thing. does the recovery console works? if you can, could you tell me how you did that edit1 ... to be true I was a bit inspired by gosh's guide and I think, when I read the guide, that I did everything right. maybe there are some limitations of CDFS that makes impossible to read the iso properly (tested in virtual machine) edit2 ... tested to run winnt32 /noreboot in the SP2 folder and it stopped that it can't find a path of some file :-O maybe thats the problem... going after

My testing so far So far I'm stuck on the graphic part of installation. I think I did everything right but in first second of graphic part of installation a messagebox pops up and saying something like: Structures of internal data of installation program are corrupted (phase 0) (it is very roughly translated from my mother language). And what I did? 1) copied I386 SP1 into SP_1 2) copied I386 SP2 into SP_2 3) copied WIN51,WIN51IP,win51ip.SP1,win51ip.SP2 into "root" of the CD 4) maked w2ksect.dat into sp_1.dat and sp_2.dat and hexed string I386 info SP_1 and SP_2 5) hexed setupldr.bin as said in many threads 6) maked winnt.sif with skip EULA and ProductKey 7) used BCDW to do the multithing job bootcat.ini has this: C:\ ; Boot C: \sp_1.dat ; Install SP1 \sp_2.dat ; Install SP2 :reboot ; Reboot 8) edited txtsetup.sif,dosnet.inf,layout.inf to match the directories 9) removed DOCS,VALUEADD and in cmpnents TABLETPC and MEDIACTR I think thats all, if I remember well. If I missed something, then will add it So the part that runs in text mode is ok, Recovery console works too on both but when it comes to graphic part of installation (after first restart) then to error pops up (mentioned above) Any ideas? THX Pedro

Currently I'm thinking about making a boot medium that have SP1 I386 directory and SP2 I386 directory on it. My questions are: * is it possible to make it? * is there a tool, that could compile the boot iso, so that the files that are the same for SP1 and SP2 are physically once on the medium, but are showed in both I386 directories? - I think is it possible but don't remember the tool or how to set such a option in ISO creating tools Thanks to all. Pedro

i would say: no way... you have to install windowblinds to show the theme... so you have to find a way to do a post install or integrate somehow the installation of windowblinds into xp cd.then make a script to load you theme. easy heh?

I would say that M$ didn't support such a hardware. I saw a CDROM connected via PCMCIA years ago in a computer magazine as a advertisment on it. Do you removed PCMCIA support in nLite? Something like native support if you didn't removed it should be, but this is very not to be likely to come. Drivers are not avaible? I think not. It's not a wide-spread piece of hardware.

good to read good news. best wishes.

the it runs on battery (have a notebook of course) I would say to the theme: not to much programs running in the background (not much in the tray)

agreed I think its the motherboard... xxxPE series are not very well tested before going to shops by manufacturer and maybe you have one that have some more testing needed.