Incroyable HULK

I added the KB885626 patche because it will appear as a critical update for people having a Prescott D-0 Core CPU (even if you already have SP2) As I always said: "If it show up on Windows Update, I'll keep them on the list". Tomorrow is Patch Day and we'll see if they still show up...

Too many choices made me switch to Gentoo...

I have theses at the root of my Multiboot CD and also at the root of the source folder (where your i386 folder stand) CDROMSP4.TST CDROM_IP.5 CDROM_NT.5 and no, you don't need the spnotes and readme files...

I don't know if someone mentionned this but I tried this method with Windows XP x64 Edition and it doesn't work. I mean, if you provide some drivers, setup will load the files but will halt a bit later telling you it was unable to find any hard disk. Maybe it would work on a machine which trully need the extra drivers you added but it doesn't work under simulation (using Intel x64 Raid Drivers under VMware 5.5 Beta).

This is a never ending debate but here is my insight: I've been active in computer hardware for the last 6 years and I can tell you I still prefer Intel in the long run. Why??? Chipset stability. Intel has the most stable platform on the market (except for the i820 chipset if some of you remember the SDRAM issue with the PIII). AMD has done a great job starting with the Athlon lineup a few years ago and I beleive they have the BEST processor out there today. The fact is that the Pentium 4 with his netburst architecture is a total failure. We all knew back then when they launched the P4 at 1.3Ghz and using highly priced Rambus that something was wrong. Even a PIII 1Ghz had the same performance as the P4 1.5Ghz. And now, the gap is still increasing since a Pentium M (PIII somehow based) running at 2Ghz is able to beat a 3Ghz Pentium 4 (except maybe for Video applications). Even Intel had to admit : http://it.slashdot.org/article.pl?sid=05/0...137&tid=218< AMD saw this comming and they started naming their processor based on a performance comparison instead of the real Mhz Clock. So here is the deal, go with a AMD CPU on a Intel chipset (i666 platform) Seriously, if you go with a Intel CPU, go for a Intel chipset otherwise you lose the advantage of a Intel Platform. This is what I buy at work. If this is a personal computer you are looking for, you should consider a AMD cpu on a nVidia chipset. They have proven to be stable enought. Don't go for ALI & SiS chipset BUT I must point out that 80% of the PC out there are Intel so guess on which platform your preferred software is designed on (and debugged first). I compared a AMD64 2Ghz and a Pentium 4 3.4Ghz last summer (2004) and I can tell you they give the SAME performances. Hope this help

Trully impressed! Do you think it would be possible to adapt this script to move some big files, like a ISO, by checking the total size of the file to be transfered?

WoW 10KB !!!

Ok, nevermind, I had the time to try with a simple winnt.sif file and I am at stage T-24 without a hitch now... Are you guys able to decompress your drivers at stage T-39 with a 7zip SFX archive like:

I guess you already had the WIN51IP file (from another Windows) at your root so this is why you didn't get this issue... Anyway, I still have a few problems: 1- I noticed my drivers didn't get uncompressed at the beginning of the GUI part (T-39) 2- I had to manually click next 3- setup get stuck somewhere at T-33 or T-37 stage... I'll try with a "simpler" winnt.sif file tomorow

Wohaaa You won't beleive this! I took a ride into the txtsetup.sif file and I found this: So I added a dumb WIN51IP and WIN51MP file at the root of the CD and inside \SETUP\XP64\ folder and guess what? IT'S WORKING! My WMware simulation is going on... the only thing is that I had to press next after the first reboot (at the GUI) ... I'll keep you updated, it's still running

Affirmative

Well, still no luck... I used your boot folder and your path but it does exactly the same This is what I get in WMware and on a real computer: This is to show what files I have... It's like the SetupSourcePath entry is ignored... I don't know. If I put the I386 and AMD64 folders at root it will work (but not unattended unless I throw my winnt.sif in there) I am using a VLK CD I got from Microsoft a few months ago... *** EDIT *** I don't think this could matter but I am not using the BOOTSECT.DAT file provided by microsoft, I edit the w2ksect.bin (like I always do) provided with EasyBoot... anyway, I get to the setup so I don't think this has any influence...

Have you checked before allowing the download your winnt.sif file? So if I use this boot folder, I need to put the I386 and AMD64 folders in a \SETUP\XP64\ directory?

this is EXACTLY what I have done! I renamed the $WIN_NT$.~BT folder to X4E1 I added the original AMD64 and I386 folder inside a \SYSTEM\XPX64EN\ folder In my X4E1 folder, I ajusted the SetupSourcePath inside the txtsetupsif file to this location (\SYSTEM\XPX64EN\) In my X4E1 folder, I edited the setupldr.bin to change I386 and i386 to X4E1 (7 occurences) In my X4E1 folder, I added my winnt.sif file Am I missing something? Edit: if your stuff is working, could you make a download of your BOOT folder?

I did include the WIN51 and WIN51IA at the root of the CD and at the root where I moved the I386 and AMD64 folder (inside a \SYSTEM\XPX64EN\ folder). What I am telling is that even if I edited the SetupSourcePath of my txtsetup.sif file inside my boot folder, (to reflect \SYSTEM\XPX64EN\) the installation is still going into the I386 and AMD64 folders at the ROOT of my CD, not the one inside \SYSTEM\XPX64EN\. On a "regular" 32-bits system, I would do it this way and then throw my winnt.sif file inside my boot folder (no need to add it to the I386 folder). I suppose this way of doing business is now gone... I'll have to put a bunch of renamed AMD64 & I386 folders at the root of my CD, and keep a bunch of boot folders at the root and throw each of my winnt.sif files inside theses boot folders as well as the I386 folders...

When you are editing SETUPLDR.BIN, are you changing 5 occurence of i386 and 2 occurence of I386? I am asking because I did it this way, then I changed the SetupSourcePath of my txtsetup.sif file and when I boot, setup is asking me to insert the Windows XP x64 CD-ROM right away... unless I put the i386 and AMD64 folder at the root of my CD but if I do so, it won't go unattended

hmmm... no comments

Hello all, I was wondering if anyone could indicate a good source of information about IT management... especifically about the number of technician you should have for a given number of Computers/Users. And tell me how it is at your place... At my place, we have about 450 users and 700 computers and we are 3 technicians (also 3 professionals but don't count on them). We have to take care of everything including: customer support, installation, re-installation, configuration, network, IP telephony, inventary, licensing, etc... The only thing we don't do, is to "teach" how to use applications... we can help be we are not there to tell how to integrate a spreadsheet into the word processor...

Solved (Is the Program Files folder on another drive than the one that the WINDOWS directory was installed to ?....from MS Newsgroup, Mowgreen MVP) http://support.microsoft.com/newsgroups/ne...&sloc=en-us&p=1 I do have my Program Files folder on the D:\ drive and I didn't had any problem with the latest hotfixes... do you?

How do you edit setupldr.bin in that case? Are you only replacing instances of I386?

Have you followed the guide properly? Unattended CD/DVD Guide Homepage The same principles apply to Windows 2000... (well, most of them )

I guess we can use GOSH's method to obtain our BOOT folder... I did that a while ago and I got the following files from $WIN_NT$.~BT <DIR> system32 1394bus.sy_ acpi.sy_ acpiec.sy_ adpu160m.sy_ adpu320.sy_ aic78u2.sy_ aic78xx.sy_ aliide.sy_ amdide.sy_ arc.sy_ atapi.sy_ biosinfo.inf BOOTSECT.DAT bootvid.dl_ cdfs.sy_ cdrom.sy_ classpnp.sy_ cmdide.sy_ c_1252.nl_ c_437.nl_ dac960nt.sy_ disk.sy_ disk101 disk102 disk103 disk104 dmboot.sy_ dmio.sy_ dmload.sy_ dpti2o.sy_ drvmain.sdb fastfat.sy_ fdc.sy_ flpydisk.sy_ ftdisk.sy_ hal.dl_ hidclass.sy_ hidparse.sy_ hidusb.sy_ i2omgmt.sy_ i2omp.sy_ i8042prt.sy_ iirsp.sy_ intelide.sy_ isapnp.sy_ kbdclass.sy_ kbdhid.sy_ kbdus.dll kd1394.dl_ kdcom.dl_ ksecdd.sys l_intl.nl_ migrate.inf mountmgr.sy_ mraid35x.sy_ ntdetect.com ntfs.sys ntkrnlmp.ex_ ohci1394.sy_ oprghdlr.sy_ partmgr.sy_ pci.sy_ pciide.sy_ pciidex.sy_ pcmcia.sy_ ramdisk.sy_ sbp2port.sy_ scsiport.sy_ serenum.sy_ serial.sy_ setupdd.sy_ setupldr.bin setupreg.hiv sfloppy.sy_ spcmdcon.sys spddlang.sy_ storport.sy_ symc810.sy_ symc8xx.sy_ symmpi.sy_ sym_hi.sy_ sym_u3.sy_ toside.sy_ txtsetup.sif ultra.sy_ usbccgp.sy_ usbd.sy_ usbehci.sy_ usbhub.sy_ usbohci.sy_ usbport.sy_ usbstor.sy_ usbuhci.sy_ vga.sy_ vgaoem.fo_ viaide.sy_ videoprt.sy_ volsnap.sy_ watchdog.sy_ wd.sy_ winnt.sif wmilib.sy_ 102 File(s) 7,213,922 bytes

Well, I would have updated the first page and given you the credit...

I would also like to know HOW you go it working... but I would also be happy with it if you post the modified file.

I did the A+ certification a few years ago while I was working at a local computer shop. All I can tell is that this test is fantastic! This one is divided in two parts, one for hardware skills and the other part for software (OS) skills. You have to pass BOTH of them to obtain your certification. The thing I liked about this test is that you need experience to go thru, only reading without touching hardware would be almost impossible to pass the hardware test... same goes for the software part. I would STRONGLY recommend Mike Meyer's Passport A+ Certification book. I don't think you need anything else (beside some experience). Good luck