likuidkewl

If you don't mind was it an issue of the order of hotfix's or something else?

So what are you results resetting the cmos and bios together? Because it is starting to sound like something else is wrong too, have you checked you Power supply voltages? Just as a side note, if it is new, tell HP you are a new computer user and you didn't know that refrigerator magnets weren't supposed to be stuck to the case, and could they fix it.

That's all they say on their site, and you wouldn't be direcly linking.as for winamp.....only one way to find out Yeah me too, I kept getting a SQL server error. Now I know why. @ Mac-- Have you gotten ahold of you lovely support personell? lol

Try clearing the CMOS jumper could you please explain how to do this... i've found the battery... many thanks It could be soldered to the board so be careful while trying to remove it, if you cannot remove it try hooking up some alligator clips to the terminals and ground out (earth) the batteries voltage. (This happens because the voltage will follow the path of least resistance.) I know common sense but some people are not aware.

Try clearing the CMOS jumper, then remove the battery on the Motherboard for about 30 seconds to 1 minute and then try again.

I use VPC for the bootup things, like menu's and first run batch files, but for a total install test I use VMware 4.5, just my $0.02

*notice the /makelocalsource, this will copy the install files over to the destination computer before it begins installation, this way networktraffic is reduced. This can be handy when dealing with multiple computers that you want to install. the EXIT command on the last line is also required to make winPE reboot. step 3: by this time your distribution share should look like this: 1 folder named i386 (this would contain your $oem$ folder) 1 file named unattend.txt 1 file named unattend.bat now boot the destination computer up with the WinPE cd... step 4: after booting the dhcp server assign an ip adress dynamically, and then give you full controll of the command line. type the following on the command line ; net use x: \\servername\distributionfoldername servername = name of your file server (find out what yours is) distributionfoldername= the folder that contains the i386 folder.(by default "windist") step 5: then switch to x: (or a letter you might have used in the net use command) step 6: type the following ; unattend.bat step 7: sit back and watch your installation run over the network I hope this helps you in some way................... PM me if you got any questions. greetz Thanks for taking the time to type it out. I just didn't feel like it.

That worked right?

Link added: How to Boot the Windows Preinstall Environment from a RIS Server by Using PXE-Enabled Clients

I have not used it in VMware, due to the slow install of Os's, so my suggestion is to burn it to CD and give it a go.

Is your network adapter supported? If not try to add the files needed.

In your PE folder delete, bootfix.bin.

welcome, but you posted in the wrong forum.

Although remote logins are disable by default for accounts with no passwords yo might want to double check that in your secpol, also admin should ALWAYS have a password, I have had this discussion before and you can remotely mount IPC$ shares on admin accounts without a password.

This can be easily applied to a netowrk install, Microsoft knowledge base has alot of articles on how to do it, as well as these forums, via RIS,WinPE, etc., All you really have to do is move placement of your I386 folder and point to an unattended setup file. Check out this KB article: http://www.microsoft.com/resources/documen...icb_ui_ubiq.asp so when you call the install file say using winnt32 will look like this: *Note yours will look different depending on your paths* <SERVER>\<SHARE>\I386\winnt32.exe /s:%SetupFiles% /unattend:%AnswerFile% These variables are set by these: set AnswerFile="<SERVER>\<SHARE>\I386\unattend.txt" set SetupFiles="<SERVER>\<SHARE>\I386"

Yeah my 1 and 1 is fine, and it's FREE!

You just want to ban everything!

I would go with flash instead

Media Center only comes OEM from Large PC makers, ie. Dell, HP, Sony, etc., and the pc's it is loaded on must meet certain requirements, TV tuner, remote, etc. You cannot legally get it with out buying a media center PC.

Very nice work! Much appreciated.

Longhorn is the new concept and granted alot will change, but Blackcomb is the next server OS so, 2003 will be around for a while. I didn't mind NT4, but once we started using 2000 I was never going back, 2003 I feel is only a slight improvement over 2000, I right now don't feel an upgrade to 2003 is as pertinent as Microsoft would like you to believe. Atleat not until Longhorn. Just my opinion, but in reply to the actual topic, I will not miss it, good ridance.

This KB article is my best guess: http://support.microsoft.com/default.aspx?...kb;EN-US;315341 This would be your best bet I am assuming: Enable Boot Logging: This option enables logging when the computer is started with any of the Safe Boot options except Last Known Good Configuration. The Boot Logging text is recorded in the Ntbtlog.txt file in the %SystemRoot% folder

I am a junky I suppose, I come hear mainly to learn and to spread what knowledge I have... Albeit is only a little...

Will someone close this thread(s) it is all just useless b**ching.

Try this: 1. Install and Windows Recovery Console 2. Copy C:\Cmdcons\Bootsect.dat to C:\Bootsect.dat 3. Add this line to your boot.ini C:\BOOTSECT.DAT="Microsoft Windows PE" 4. Copy i386 from CD to C:\Minint, you must name the directory Minint