Vel Straty

Thanx! airmr! I'll try it!

Hi everyone! I've been working around to fashioning my XP Pro to look like how I want by editing the .dlls and .exes (i.e. replacing the bitmaps). However, I cannot find the dll that is used for the LOGOFF. The one that I'm talking about is the one that when you choose, START -> LOGOFF, and a dialog kinda stuff appears and lets you choose whether you want to change the user or just simply logoff. I would really appreaciate it if someone here new about how to do this. Sorry if it was discussed earlier but I wasn't able to find it.

Just put all your drivers inside one folder and it shold work fine as mine does! You don't need to make any dirver\000_lan, driver\001_graphic, e.t.c that'll make your winnt.sif longer, I just make mine driver\all, and that's it!

I don't know if this will work for you but I use a printer which is not included inside the WinXP cd (Canon BJ S330). I install it using the unattended (winnt.sif) stuff. Usually, if you install some device, it has to be turned on but even when the printer is not turned on, it installs by it self without any dialogs appearing in front of me asking for Yes/No stuff. If you have those original installation diskettes of your HP 720C, why don't you use it for the unattended installation? Or maybe you can do this and figure out which ones are needed by checking out the drivers when you do the printer testing which prints out the driver lists. Hope this helps, but if it didn't try other pplz method.

Hello everyone! I'm new to this thread. I would like to know the settings for the taskbar as I'm making an unattended WinXP instalation cd. I've checked the forums but had no luck on finding it so I've posted this. Sorry if it is already discussed. At every Windows Xp or 2000 computer, I see the taskbar at the bottom of the screen. I wish to have it on the top of the screen as a default setting for my pc for every user when I use it in conjunction with the unattended install of WinXP. I've checked it out with REGSHOT but of course, it only shows it for the current user settings. Do any of you know how to this? Thank you in advance!

In either one, VPC or VMWARE, I get a BSOD at the GUI portion of the installation of WinXP Pro (SP1a). But the error doesn't seem to occur when I install it the normal way, meaning the way you install it normally by booting from the CD-ROM drive from the Black & white screen. The BSOD that I get is something like PAGE_FILE_ something .... If you have a CD-RW, try it normally by using the CDRW or DVDRW.

I've read that the folder numbers 000_Something, 001_Something2, e.t.c. will ensure that the drivers will ensure to install in the order of the numbers but I've had no problems since I put all the drivers into one folder, $OEM$\$1\DRIVERS\ALL And by the way, I use the nForce drivers.

A thread a loooong time ago. Who remembers it. Anyway, the prodspec.ini as you requested. This one is for the XP Pro SP1a ; ;Note to user: DO NOT ALTER OR DELETE THIS FILE. ; [SMS Inventory Identification] Version=1.0 [Product Specification] Product=Windows XP Professional Version=5.0 Localization=Japanese ServicePackNumber=0 BitVersion=40 [Version] DriverVer=07/01/2001,5.1.2600.0

Thanx for the reminder but it has already been stated here. But it's inside the forum maze so I think it'll be a good reminder for the other Jap WinXP XPCREATE users. If you wanna use the xplist locally, follow this link. By the way, do you get an error when installing the XPCREATED WinXP cd to your computer? The error for me most likely occurs when the GUI portion of the installation starts. Hows it going for you? Hope to here from you.

You should check it out at www.google.com Maybe this link shall make you happy. It's a google cache for the khost.exe stuff.

Or you can use your own download list locally and delete or comment out the line where it writes about the Baseline utility. Then run XPCREATE.

What kind of internet connection are you using? I've read in some papers a while ago that in Windows XP, sometimes the internet connection goes down and comes back again without any problem if you're in a wireless environment. In the article, it also said that there was no cure for that and who ever wrote the article asked to the M$ employee that for right now, there's no way of solving the problem. Hope it's fixed in the coming SP2. Best luck to you

Well, if your problem is just to install the win2k OS, then why don't you install it? But if you want to work a way around to installing the win2k OEM for compaq pc, there's no luck on working a way around it. Buy a new one!(as MS will surely tell you to). But for us consumer's, our wallet is tight, I don't know how the OEM OS's say on their small letter LAWS, but if you can build a PC, why don't you put all the motherboards e.t.c. into your old compaq box. In a way, I guess it will not violate the MS laws, and further more, your HD went down on you right? When it doesn't work, you gotta exchange the old to the new one, so it should all be ok!

GreenMachine, I know what you mean by security reasons to only DL from the MS web site. But isn't the MD5 checksum there to check if it is the real one or not? Well, I can't code like you do so since I don't know how to run the batch file stuffs, ( well used to know it back then), so I and the many other can only post requests or fix something that is very easy. When I got the time, I'll try to do the coding from the one that you've created to let it use some kind of a downloader so that it can do multiple downloads at one time. Not all of us has a broadband net line but using a downloader, we can DL many at once which many of the people might want. If this goes against your will GM, sorry about that, but like you, and many others participating to get the XPC go good I'll keep on trying for it to run better! Have fun at your vacation location. Now, I'm going back home to the US for some vacation! We all gotta have some rest for our soul!

Thank you GreenMachine for your kind word. The XPCREATE works fine if I comment out the "Q832894.exe" from the SVC-HF2 list. But however, when I use the MS Baseline Utility 1.2 which got installed from with the XPC, I get some hotfixes that show as not installed even as I got it inside the XPCREATE.ISO that the XPCREATE.CMD under the i386/svcpacks. And also, when I try to install Q832894.exe after the whole WinXP setup process, WinXP goes bye-bye, saying something like SHLWAPI.dll is doing a bad job.(Look Here for the errors). But I haven't tried the orginal unattended method that many of us probably has tried before using your XPC so I'll try that method and report about it. (I think I've setupped the WinXP near 20 times already after the first try of XPC! Well, my HDD is doing a good job on not giveing up on me!)

Dustinwmew, I used VMWARE and MS'S VirtualPC but the only thing I get is an error. Each time I get and BSOD when I try to install. The problem is not the same as yours but when I try it w/o the emulators, meaning installing it normally, it works very fine, no errors of course. Make a back up of your system if you only have your main pc to test it with, and you should try the XPC built WinXP. To avoid any kind of errors, try it with out the $OEM$ or anything except the original xp. Good luck!

TenaciousMetal, As GM says, there was no link for the SP1. Even if we show you the codes for the stuff, not adding the code to your hflist will not solve the problem. Well, sorry for the late response. The code is HERE. There were two links that I found for your Italian SP1a. Both were from inside the M$ website, one short and another one had a long URL. And the third one that you can link to can come from the WindowsUpdate site. If you find it. I chekched the above two's MD5 but, of course, it was the same. Maybe, for is some reason that the MS server would not response at all, somebody can be nice enough to host their updates in some manner. And for the XPCREATE.cmd to download from multiple places can make the users life easiere. But of course then, it wil make the coders life harder.

Why don't you copy and paste the XPCREATE.CMD's window on to here? That should help discover some problem too. If you don't mind, attach the log file if there is one. I might get you to help in some way if I can.

Well, TenaciousMetal, for that question I don't know about it. But I use the same parameters, just in Japanese but it works fine.

Here ya go! [OSInfo] SOURCEVER=XPP WINLANG=ITA CURSPVER=1 CURSPURL=http://download.microsoft.com/download/6/a/7/6a727e5c-c84b-45ef-b943-b0080acfe352/xpsp1a_it_x86.exe CURSPMD5=749ba827bd053db6f9dc821ab274b0ba CURSPPATH=SPACKS\xpsp1a_it_x86.exe This should be right.

Updated version of the Japanese XPCTHLST.txt. The error that was created during the startup of the GUI mode just before the t-39 GUI setup was caused by "Q832894.exe". By excluding it, Windows XP Setup finished w/o errors. Look at Error page for the error. Attached is the modified non-error Jap-localized XPC list. XPCTHLST.zip

XPCREATE is only out in an English version as GreenMachine has an English version of Windows XP as I assume. I use A Japanese version of WinXP Pro, how about the rest of the users here? By knowing what Windows' are out there it might make some people out there to make XPC a better one so tell us your language!

Well, enuffsaid, I'm new to this MSFN forum so I don't know much about what's going on other than inside the XPCREATE place. There's a BIG, VERY BIG BBS place in Japan called 2ch, but that place is just a spammers paradise. You can get information there but calculating the time and cost, its not worth searching for information or neither contributing to something there. But here, as for now, this MSFN place doesn't seem to have much spammers so that is why I contribute, not much but things I know. Anyway, going back to the localized version as the thread says, I'm still figuring out the way to install WinXP created by XPC. The only thing that I've found out was that the Q832894.exe was causing the problem to stop setup at the t-39 point of the GUI setup. Will be back again with cause and effect data!

No need to say it man! > enuffsaid Just had a little time of my own to share!

You can check out on any file's checksum by using this software, WinMD5sum. It's just easy as D&D. Anyway, here are the md5 checksums for the following Dutch hotfixes commented by enuffsaid. File Name : Q831167.exe URL : http://download.microsoft.com/download/7/e...b3d/Q831167.exe MD5 : 3f4face1c3a1b32aa52e9f63b41ba8af File Name : WindowsMedia8-KB817787-x86-NLD.exe URL : http://download.microsoft.com/download/d/a...787-x86-NLD.exe MD5 : ab1ecf6bc00313608d79d2b67e51265c