lukar

That's what i'm going to do.. I have Epox Nforce 3 Ultra, AMD 3000+ running 2.26, 2Gb of RAM, NVIDIA 6800GT and SB Audigy Platinum ZS2 and that's all I got. Network card is integrated and NVIDIA provides complete 64bit driver package for NForce 3 chipset. This station i don't use for nothing, absolutely nothing but gaming. I don't even need antivirus...

Thanks...it answered my question. It means i can give it a try.... Running AMD64 here...

Nobody answered his question! When you install Window XP X64 Edition it creates two folders called Program Files and Program Files (X86). 32bit applications including the games you have to install in Program files (X86) folder, and Program Files folder is for 64bit applications. So, I wonder like the guy who posted this, what will happen if I install 32bit game on second hard drive or second partition. Let's say D:\Games\UT2004 for example? Are you able to do something like that, or you're gonna be forced to install it in C:\Program Files(x86)? If so...WinXP X64 is not for me, actually not for anybody...

Actually not it gives me one error....

Use NLite -> Service Pack Slipstreaming and point to folder with your IE 7.0 installation file and should work

Yeah... I extracted it, and tried to edit the bootsector, but i'm getting errors...

The thing is that this multiboot CD is done without using script...that's the point...

It's the Microsoft way of doing it...i guess... So, CD root looks like this ENGLISH->WIN2003->STD,ENG,WEB 3ENE 3ENS 3ENW WIN51 WIN51IA WIN51IB WIN51IS And that's all. Boot screen looks like regular Microsoft boot screen. You have message press any key to boot, and then you have simple list of STD, ENT and WEB to install. I just don't get what's the trick here...

I have Windows 2003 Server 3In1. I checked out the CD content, and there is no scripting used, nothing. The files are not hidden! It contains English folder and inside Win 2003 and inside full installation for STD, ENT, WEB. On the root folder there are STD, WEB, ENT folders as well as WIN51 etc files...and that's all....

I'm not gonna install it, just want to put it into my multi dvd boot for the future use...

The way I did is I created boot screen using Autoplay Studio. I took the screenshot of it and resized the image to 640x480 24bit bmp (Adobe Photoshop, saved using max quality into jpg format) and then I reopened using Paint and just resaved the file using 24bit bmp format. Then I converted to *.csi extension, and placed into BOOT folder. When the computers boots up from DVD it loads that image. Just make sure that the corresponding letters (choices) on the image matches to the cdshell.ini script, and that's all. It's not a big deal...

The procedure should be the same, but my CPU doesn't support 64bit OS, so I can't get the BOOT Files

It's autoplay media studio 5.0. You can download trial version... It's a bit different than autoplay media studio 4.0. You don't have to worry about the location of your project and additional resource files such as images, icos... When you click the publish button, you choose hard drive/folder and point to CD\DVD root. The studio is going to copy and build files and you're good to go. Media Studio 5.0 is like visual basic, but it's simplified. You can either code in the codes or you can find appropriate function from the lists and assign to your object. I used resHack do get the images and icons from longhorn setup.exe, shell32.dll and slate.msstyles files. You don't need to know anything about programming. It's all about imagination and patience. Good Luck

Send me your DVD folder structure, so I know in which folder is what windows operating system... I will make one for you over the weekend, I promise All you need is to extract zipped files i sent you to your installation cd/dvd folder, and then make an image.

What do you think?

I Just received it, and it's working great for my windows 2000 pro/server. Your current hotfix list is really helpful, especially because you provided direct links to get those files... Great Work!

How many days takes to process email before you get download link for XPCREATE? I send mine yesterday.. Thanks

I don't think I'm reinventing the wheel, because my method is *cat, svcpack.inf free... This is updated package. It contains hotfix for windows messenger (mmssetup.cab -> I didn't repack this but directly injected the new windows messenger executable file), and also WMP10 ( I used wmp1.1 script ). It's tested and it's working.... http://bis.midco.net/lradunovic/HFSP2.zip It applies to Windows XP Pro, Home SP2 English version. Replace all files in I386, or you can directly inject the files via Magic ISO, so you don't need to unpack your image and create a new one. The reason why KB885835 and KB885836 do not work is that some of those files are located in more than one location. So I guess WU checks the certain cabs as well I will sort this out by tomorrow, hopefully...

so what you're saying is that I'm right in the WU doesn't properly detect the install, and WFP doesn't see them as valid? There already is a excellent pack for hotfixes by RyanVM. nLite also automates the process (for post-sp2 hotfixes). Also... How is that the best option? I take it you're meaning to replace the files in the SP2 network install, then integrate the files? SP2 integrate SHOULD detect the improper files and error out (CRC checking) and if it doesn't, you're back to the problem you currently have. WU doesn't detect the install, and WFP doesn't see them as valid.I'm sorry i didn't see you message again... You're wrong about SP2. That's what I'm doing now...It didn't get any error message. It's not about version of file, but it's about certification of file, of course if we are talking about two same files "technically". One of them is certified and the other not. The only certified file is going to pass sort of file verification. As long as the file is certified it's gonna be cool. If you put two same files and one is a newer than the other any Microsoft applciation will install a newer one. This is the concept which Microsoft holds since the beginning. For example: I just replaced messenger executable file and repacked and insterted in sp2, and after that I integrate sp2 and everything went smooth! Now, I'm installing windows xp to see is everything ok as well as for other hotfixes except one for .NET framework which is not really windows update fix. I'm gonna soon post some screenshots... I apologize for two posts...i didn't quite read your comment about SP2 thing... I appreciate every feedback...

so what you're saying is that I'm right in the WU doesn't properly detect the install, and WFP doesn't see them as valid? There already is a excellent pack for hotfixes by RyanVM. nLite also automates the process (for post-sp2 hotfixes). Also... How is that the best option? I take it you're meaning to replace the files in the SP2 network install, then integrate the files? SP2 integrate SHOULD detect the improper files and error out (CRC checking) and if it doesn't, you're back to the problem you currently have. WU doesn't detect the install, and WFP doesn't see them as valid.The are valid and Windows XP doesn't make problems with it, neither there are strange WU hotfixes of 0kb. Windows File Protection box does not pop up during installation, and there is no reason for it since those are Microsoft Certified Files, not some hack. If you're getting problems, I would check out a copy of your Windows. As I said, after applying the patch 5 hotfixes remains unpatched. Right now I'm testing out something, and I'm hoping that there will be 0 wu updates after installation Stay tuned

I didn't say it's perfect...but takes care of most post SP2 hot fixes. I'm still working on this, and i guess the best option would be to integrate those files into sp2 installation folder, and then integrate sp2 into windows xp....or maybe not. I don't deny that some hotfixes requires registry entries, but 80% of them do not require it. So, 8 of 10 hot fixes would work this way which is pretty good method. It saves you a lot time of making SVCPACK thing and so... I used makecab to compress those files. This method only applies to clean Windows XP SP2 English version, and no merging SP2.cab into DRIVER.cab.

I guess this little package kills the purpose of this site...

It's nothing intentional...I use to click add reply button before I even finish my thought....it's something i have to deal with it... The other post is there by mistake....

It's tested and it's working....

WU will recognize it....don't worry about that!!!