Tripredacus

It's impossible to know everything, so we all get answers from other people!

Did you know that "Du Hast" means "I have" in German? Except the proper German title for that song is "Du Haßt", or to translate "Du Hasst" which means, "I have." The original song is about saying no to wedding vows, but the English version was changed, and I can't stand it. lol. I have that song looping! I so bet. For me: Industrieplast: Knochenangst

I'm trying to figure this out but it just isn't working for me. As I said previously, I no longer need to disable ALT+TAB after switching to winpeshl.ini loading functionality. However, now the request is that I remove the button I had to launch the command prompt. They want that button to not be visible but use a key combination that launches that program. So my question is, how can I use that function to launch a program instead of doing nothing? I have researched this function online but I can find no specific examples. Most likely because people use these scripts for games and online websites, and putting in code that opens a program this way (on the internet) would likely be considered malware of some degree.

That is the normal thing that would happen. You can take an unmodified boot.wim from a Vista (or 7 or 2008) install DVD, stick it in boot images, and WDS will know what to do with it. So this makes sense that you can take it and put it on a DVD and it starts to install. To deploy using a DVD like this, you are going to want to go the route of Distribution Shares and Configuration Sets. http://technet.microsoft.com/en-us/library/cc749066.aspx

Also, make sure you are running off the AC adapter, running installs off battery do not usually end well.

OK that is weird right there. My 2003 server x86 and 2008 x64 both detect clients as x64. I currently force both servers to use the x86 boot file, but this is done by manually changing the path and not changing a rule. You can see this setting in my tutorial i wrote a while back: http://www.msfn.org/board/index.php?showtopic=113927

No, I wouldn't recommend going that route. Compare all the settings between the two setups to see if you missed something. That may include WDS, Domain Group Policy and/or DHCP settings. Also, can you confirm if all MININT clients fail to boot off the 2008, or just some?

Welcome to the MSFN! If you have any specific questions regarding the best practices and licensing limitations and allowances, you should contact your Microsoft account rep. Different tiers and partnership programs have different licensing requirements. Your account rep would be able to get the best and correct information regarding your question.

Try to map a network drive using the fully qualified domain login, then try to run your program.

You didn't mention what bit the 2008 was. Try this out on the 2008. Copy your pxeboot.com from the 2003, rename it to say "2003pxe.com" or something. Find where you current PXE boot file is located, you can get this name from your Server properties. Stick this renamed file in that folder. Next, get the MAC Address for the client that won't boot properly. Next, add a WDS exception for that client to use your 2003 boot file. Reference the following: http://www.msfn.org/board/index.php?s=&amp...st&p=849425 After these changes, try to pxe boot the client. See what happens. note: This is an idea that just popped into my head. I cannot gaurantee that this will produce any results.

Some NICs will allow you to get an IP but not boot. Can you post which NIC it is, and also if its onboard, which board it is. In the past I've experienced two different issues: 1. The NIC was an RTL8201 which is a virtual device and does not work in Win PE (any version). 2. The pxe code is out of date or corrupted. This happened initially with an AOpen iGMT-LA motherboard. I had talked to Realtek Engineering department and also AOpen. This was fixed by getting a BIOS update for the motherboard. It should be noted, at this time there was no BIOS update for the board, and AOpen made a custom beta version to use. They had since fixed this issue with these boards and a BIOS update is no longer needed. So post what you have and we'll go from there.

The HTA design is nearly complete. I have the following to now do: 1. Remove the button that allows the user to open the command prompt, and add a function that would launch the command prompt via a keyboard shortcut. 2. Test launching the HTA via winpeshl.ini. This will remove the need to disable ALT + TAB since there would be no command prompt behind the program. Unfortunately, I cannot post the code for this HTA any longer because it has now been branded and is the IP of myself and my company. I also got to learn some good Photoshop skills today. Man paths were frustrating and confusing at first but now I wonder how I had lived without them!

I did some testing. I concur that the MININT cannot see the option 12 information. However, it can see the Option 15 information. I set a reservation on my server and added Option 15. After getting an IP, the string I typed in appeared under the Connection Specific DNS Suffix in ipconfig. I also tested to make sure that the MININT was capable of accessing the domain resources via hostname and this also worked. I also noticed that when you make the reservation, the name you type in for it changes once the computer boots to PXE. It changes to its MININT name that the PE generates as the hostname/computer name. If you rename the reservation name to COMPUTERNAME.DOMAIN and reboot the machine to PXE it may do the above instead. I'm not sure which it was because I unwittingly did both options without testing them independently.

If you look at the properties of the NIC in Device Manager, it has a description box. Typically normal operation will say "This Device is Working Properly" but if there is a problem, it will show error codes. A true case of "hardware is bad" is when Device Manager shows a Code 10. Code 10 usually means you have a driver installed, but see a message that it was unable to start the device. This is caused by it either being disabled in the BIOS, a resource conflict (rare nowadays) or that particular part being bad. For some motherboards, even if the device is disabled in the BIOS, it may still be detected and show a Code 10. You can also get a Code 10 if you have forced a driver to install for a device that isn't present in the system. For example, if you had the wrong network driver and forced it to install, it would give an error even if it could see the real device. If you have ever experimented with driver editing, you have seen this happen. You may have other errors. There are two to three error codes that are specifically driver related, such as Code 1. Knowing what Code you are getting is a good start for troubleshooting. Here is the KB for the codes, ask about any specifically if the Microsoft explanation is confusing: http://support.microsoft.com/kb/310123

You should be able to just run them from the run box or make shortcuts for them. My computer used to dual boot XP and Server 2003 (back when it was called .net) Enterprise RC2. 2003 was installed on the D: and I had installed programs on there that were not on XP. After I removed 2003, I did not delete the Program Files folder. And I now have icons in my quick launch that run those programs installed on the other drive. They don't seem to have any problems running, but each program is different. You'd have to try them out and see what does what.

I want to step back a minute now, presuming this isn't related to your other thread. I want to understand what you are trying to accomplish. Tell me if I am wrong. When you boot your MININT, it uses a reserved IP address. After loading the PE, you want the MININT to query for its specific hostname that the server has stored for that IP address. But why does it need this information?

OK, this would be what I recommend. By default your PXE option should not be available. Since you are in a school, you should already have inventory information for your system, which (I would hope) includes the hardware (MAC) address. For all of your domain computers, this information should be included into Active Directory. Your default boot option in WDS should be: Boot\x86\abortpxe.com. Then, when you know you have to re-image a certain machine, you put in your exception (in my previous post) to use one of the other options for PXE. Just make sure that if you ever replace a system, a motherboard or upgrade/replace a NIC that you update the hardware address in Active Directory.

I've got the following on my radar: Fallout 3 Far Cry 2 Crysis (you've got this already) Crysis Warhead GTA IV

Hmm, not sure if you can do this with a notebook, but nVidia CPL lets you specify a custom resolution. It doesn't matter if this resolution isn't the one you want. When you set a custom resolution, it makes keys in the registry. Then you can change those keys to get any resolution you want. See the following for reference: http://forums.nvidia.com/lofiversion/index.php?t54692.html http://www.avsforum.com/avs-vb/showthread.php?t=859819

I used to use those little spacers on the motherboard but it turns out they aren't required. My new board doesn't use them at all, but you should use all the mounting screws that you can.

I have not seen a time when a partitions ID changed back by itself. Perhaps there is an integrity check done at some point by the HP software that changes it? Or, the BIOS has a failsafe option enabled, such as a write-protect or anti-virus option. Not sure what to do since both partitions are id 0x7.

Understand that ISPs have system requirements for support purposes only. They either relate directly to the optional software they provide, or the level their tech support will help with. For example, system requirements typically reflect the hardware requirements of currently supported operating systems. So if they start their support at XP and up, XP's hardware requirements will be used. This is because companies do not wish to continue training their reps to support end of life operating systems, especially since very few people use them still. It comes down to the amount of money spent to train vs actual use in the field. So say training costs $4,000 per person for a 1 week class. If they have a class of 30 people to train them on Windows 98, that money adds up. This becomes useless if their support center only gets maybe 5 calls for Windows 98 in one year. Then, this money spent training becomes wasted. I used the figure for $4,000 per person in a 1 week training because this was the amount my former company spent on training my class in Radius support. It is an example. I do not understand how they got that figure, but it is the one they gave to us. In reality, the true system requirements are to have a network card that runs the same speed as the network port on the modem. So you can have a Windows 3.1 PC connected to DSL and it will work fine as long as you have the network card and the drivers for it. If your computer is connected to their service and does not meet the support requirements, it doesn't mean it won't work. It just means that if you are having a problem with it, the ISP will not provide support for your computer.

Next time, before shutting down, check the Task Manager to see if you see a daemon.exe in there. If so, then go to the Services snap-in for MMC. Or you can see this in Computer Management. See if Daemon is listed there. If it is, change it to manual or disabled, and stop the service. on the next reboot, it shouldn't be running.

Yes, there are quite a few old software and hardware collectors out there. I used to be one myself but I recently lost almost all my old stuff in a flood.

Welcome to the MSFN! - I am not familiar with Bart PE, nor have seen anything called vistape.wim before. sorry on that one. - I do not understand the second question - If 512MB is not enough, then your PE has too much stuff in it. The PE loads as a ramdisk. Making your PE smaller will decrease the amount of RAM you need. The official minimum requirement for Win PE 2.0 and above is 512MB. I believe v1.x could be used with a lower amount. You can try downloading the WAIK and make a stock Win PE to see it work with 512MB RAM.