Tripredacus

A lot of people have problems with this type of thing. Have you checked the Power Management options of the NIC in Device Manager?

On the computer with no internet connection, go to the command prompt, type 'IPCONFIG' and press enter. It will list your network adapters. They will all have their own headings, example: Ethernet Adapter Local Area Connection Ethernet Adapter Local Area Connection 2 etc One of them may have the word 'wireless' in it. You can look at Network Connections to find the name of the wireless NIC. - If the IP address says 0.0.0.0, then type IPCONFIG -RENEW. If you get an error, post it here. - If the IP address says 169.x.x.x then type IPCONFIG -RELEASE, it will change your IP to 0.0.0.0. Then type ARP -D. Ignore what it says if anything. then restart the computer. When it comes back up, wait your 30 seconds after the desktop loads, and see if it says anything new. You can then do the IPCONFIG from the command prompt again to see what IP it has. If you get an error on any of the commands here (except ARP), post it here. - If the IP address says 192.168.x.x or 10.x.x.x, then post the IP address here, as well as the subnet mask and default gateway. - If the IP address says anything else, post the IP here as 24.x.x.x, (in otherwords, only type the first number group in and not the rest of the numbers, use x to hide them). Your alternate option is to set a static IP on the wireless NIC via Network Connections. You would need to look at what IP address your other computer has, and pick a different number. You then would need to input the same subnet, default gateway and DNS serverss that the other computer has. Note, that if this is the only way you can get access to your network, there is a problem with either your hardware or operating system!

Oops I brain farted there. I was secretly hoping "please not XP Home". You need Safe Mode to try to check the file permissions. But so basically, your regular user account reboots after getting to the desktop but the Administrator account doesn't? Also you did do a repair install but it did not solve your problem?

Yes, the Administrator account has ownership and permissions for your application. When you run sysprep, you then create a new user. You are using a different account than the Administrator account. Ideally you should install your program after sysprep.

I haven't tried this before, but this would be how I would start. Search the INFs for your Hardware ID. You'll need a third-party search util, or do the search on something that isn't Vista, unless you've figured out how to do string searches! To make it easy, just search for 'VEN_xxxx&DEV_xxxx'. You need the & in there, and the xxxx are whatever values appear in Device Manager under the Details tab.

It doesn't help if you don't post the message it gives you. There are several threads about Vista install DVD size issues. Here is one of them: http://www.msfn.org/board/4GB-ISO-File-Siz...mit-t87993.html

Run an elevated command prompt, then launch services.msc from it. Then try to start the service. Check the Event Viewer, it should have logged an event to say why SLUI Notification Service could not be started. Also, go into the "More Information" of the welcome screen (or right-click Computer and Properties), scroll down to the bottom and verify that it says "Windows is Activated".

There are a couple things you should try. Either put your image on another hard drive, a UFD or a network drive. Verify that ghost is working properly to apply an image from one of those locations. You need to make sure that this isn't a problem with Ghost or not. Are you using the 32 or 64bit PE?

Yes, the reason why my previous threads (here) on this subject seemed to have just stopped was because I took all further research into a private forum. I have also tried multiple programs (3 or 4 different) to capture the MBR and then reapply it, but the results never came out properly. For my case, the recovery partition used the old PE (1.5 for XP) and I was testing on whether we could apply our images with the recovery partition with Imagex instead of Ghost. So I've tried the ones that copy the MBR and ones that let you custom write it. My testing method was as follows: 1. Image a machine using Ghost, which contained the recovery partition. 2. Capture the MBR 3. Use Imagex to capture both the System (NTFS) and Recovery (FAT32) partition. 4. Create custom diskpart script to set the drives up as Ghost makes them. 5. Format the drive and redeploy images using Imagex, and using custom diskpart script. Windows always booted afterwards. I could confirm that the recovery partition was intact, had all the correct files and the correct settings, but the key to enter it never worked. If I manually set the key (using one of the MBR programs) I would get the recovery message "Protected by x" or "Press key to start recovery" but when it tried to boot to that partition, it gave either OS not found type message or a stop error. The program you are referring to, relating to XSS.exe is actually NOT the name of that program. XSS is the company name, the real name of the program is MBRINST.EXE. It is possible to get ahold of this program, but it is largely undocumented. You can find it on HP's site, it is included in a fix for Vista's ability to boot to the internet, HotStart I think but not sure. You're going to have to find this program yourself, I won't help you besides that. Proper use of the program requires switches via the cmdline. It is actually a GUI based app but there are things that are needed to be done via a switch that is not in the GUI. Now, SoftThinks does not actually have this program in the either the CD that creates the partition, or on the partition itself. This program is loaded via memory, either its functions are built into its software, or it builds the app in memory when it needs to write to the MBR. In fact, at the time of the creation of the recovery partition, their software creates a dump file that sits in the recovery partition. I can't remember the name of it exactly, but I think it has 'mbr' in the name. This is the file that the software uses to write to the MBR. So, using the app or libraries built in, the cmdline needs to be something like this: mbrinst /mbr [filename.ext] /UnknownSwitch The reason for this is because MBRINST would return the following: MBRInst. Programmed for SoftThinks (c)2001-2005 Hard drive #0 is "\\.\Physicaldrive0" using "\\.\Physicaldrive0" for MBRInst >installing new master boot record (MBR1STD (one sector, standard MBR, bo *** Master boot record installed successfully. >Updating recovery partition boot record ! WARNING: Recovery partition could not be located *** = it had more text here but its not applicable to this post. So as a conclusion, in order to run this program properly, there must be an INI (there is an INI also called mbrinst.ini) that is created in memory that specifies the recovery partition location OR a cmdline switch is used to point to the correct partition. I stopped at this point because I did not want to rebuild their Creator CD using debugging tools (like ProcMon for example) because even if I were able to get it to work, it would not be legal for us to use it that way.

I've had similar problems using Ghost on DVDs as well. You failed to mention which version of Ghost you are using. The Ghost I use (7.5) doesn't seem to like using images off optical media, and also it seems to lose the drive letter for the CD drive if using a spanned image. In other words, the first part of the span would apply, then suddenly ghost couldn't find the CD drive anymore, and the process would fail. If at the point where Ghost cannot see the CD drive, if you exit, can you see the CD drive in the WinPE?

I have written a program to static an IP address, which I can share here. Actually its really simple. You can handle this in multiple fashions. First you can use a Logon script to set the IP address. Use the following procedure: 1. Take 1 machine (a test pc) and put in your IP address info. The whole shot, IP, subnet, gateway, dns, etc. 2. verify connectivity. 3. run the following: netsh -c interface dump > c:\location1.txt 4. when the computer logs into Windows, run teh following: netsh -f c:\location1.txt This, of course, is for specific IP addresses. I use this for computers that always get the same IP, as we have a single drop to a static IP that is assigned to that drop. Now, if you need to assign different IP addresses, you may need another way to create that text file, or create different text files for different users. You can then use Task Scheduler to create a task that runs every 3 hours (starting from login) that resets the IP information to default. Example command: netsh interface ip set address "Local Area Connection" dhcp Obvious issues with this is the name of the connection must be Local Area Connection or the program will fail. Make sure to also consider the possibility that your users may shut down or power off their computers without logging off them first, which could also trigger a logoff script to 1) delete the scheduled task and 2) reset the NIC to DHCP (redundant but required). As such, you may need to use an INI, or create a file during the logon script. If the file exists at boot (when it shouldn't) the script would need to run the logoff script, and then run the logon script. My AutoIT code for inputting the static IP (I run from a USB key): RunWait( @ComSpec & " /c netsh -f " & @ScriptDir & "\location.txt" ) Sleep( 1000 ) Extra info: http://www.petri.co.il/configure_tcp_ip_from_cmd.htm http://technet.microsoft.com/en-us/library/bb490996.aspx

What version of XP?

1. Started doing what? 2. I've seen this before. In my case, it happened when you attempted to view a resource (my case desktop, your case control panel) after a process or dependency was either killed or unloaded from memory. So you get an access denied messagebox. Verify that the following services are enabled and started: SLUI Notification Service Software Licensing Network List Service

I have also encountered problems restoring SoftThinks MBR to allow the function key to properly boot into the WinRE, however since we/I am a customer of theirs, and knowing how they operate (via our intermediary) and also how making this option work involved reverse engineering their software (used to put the recovery partition on the drive originally/because they offer no custom support without large fees), I decided it was not worth the effort. However, I do know that the recovery partition needs to be hidden, have no drive letter, and have an ID of 12. You CAN set this with diskpart. The main issue is because SoftThinks' Vista recovery uses WinRE, it switches the drive types and priorities when that option is selected. Simply putting the key in (ie F11) and specifying it to boot off the WinRE partition is not enough, there is other BCD logic in there. Perhaps reading up on WinRE will help you out. I'd like to ad that is pretty silly SoftThinks Vista recovery solution is merely a customized/automated WinRE solution.

Most OEM vista loads, if they do not give you a recovery or Vista disc, (such as HP) gives you an option through their software to make the recovery discs. This option, since most computers sell with optical writers, became the norm as it is cheaper for the company as a whole. Also this is why a lot of companies provide CD based or online-only manuals instead of printed ones.

http://www.roxio.com/enu/products/dla/requirements.html Note: while searching (and supported by system requirements) there are many users who complain that DLA does not work properly or at all on Vista. When you make your disc, try using the "Make Compatible" method to see if the Vista can read that. Also while searching, I also had it in my head that there is some sort of patch or wrapper you could install (although this memory is from NT days and DirectCD) to read packet-written CDs on other OSes. I can't get myself to remember an example of what this program was called.

I got rid of all errors by changing to a different application pool. Now I get NO errors (as I said) and PHP isn't working. I'm sunk now. ProcMon shows nothing, and Event Viewer has no more errors and no crashes are happening on IIS restart anymore... Maybe its time to try apache.

I totally misread that topic title

As far as antivirus, the only I've used is Trend Micro's corporate version.

It doesn't appear that the unattend is designed to do it this way. You could write a script that uses diskpart. This is a general idea: use a wrapper to launch diskpart, and you can use diskpart commands select disk 0 select part 4 detail part running detail part gives you something like this: You could use AutoIT, for example, if you read the help page on StdoutRead, which will read data from Comspec (command line), then use trim or concat functions to get the data out that you need. I had written a script that would read info off Zend's CLI app, but I can't find an example right now. Anyways, you can pull the drive letter from that, and then write it into your XML that way. I would imagine you could use VBS or KIX or anything else instead of AutoIT.

The error he is getting is software related. Removing the soundcard wouldn't likely fix the issue. If anything, removing the soundcard software or driver package would be more helpful. I don't have the operational experience with Windows 2000 to tell you how to even attempt that, however.

Instead of running the virus scan, you can run hijackthis or an adware scanner instead to see what the cookie is.

Its possible that your MBR is busted. Usually this message you are getting means that your computer can't find the hard drive. The PXE error is because you have network boot enabled but there is no DHCP-Relay server on your network. By putting it in another computer, do you mean you tried booting off it, or use it as a data drive?

I posted the link to that HTA because Geezery used a COM Object to get the info from the WIMs, which may have been the same info you wanted to get.

You usually get this message, not because the ntoskrnl.exe is missing but likely one of its dependencies got removed, moved, corrupted or was updated by a third party. In other words, ntoskrnl needs other files to load, but if they are missing or aren't correct, it can't. Then when the next step in Windows load process looks for ntoskrnl and it isn't running, it says that it is missing. If you are lucky, yes you can replace the ntoskrnl using the one on the Windows CD. You may have to make use of the EXPAND program, and either use NTFSDOS or the Recovery Console. Also, if you happen to be on a network, you may be able to replace the file that way, but only until you change its attributes. I believe those would be -R +A -S -H. But you would have to reverse that after replacing the file, so +R -A +S +H.