Tripredacus

Does your video controller happen to an nVidia chipset?

If use smallMBR doesn't work, try this in MasterBootRecord instead: STR_BS_ERROR="Missing OS\n" STR_ERROR="MBR Error\n" STR_PRESSAKEY=" " STR_START="\nPress F11 " Also you can take out the lines starting with a semi-colon ( ; ) because they are comments. My mbr.ini files do not have those comment lines in them. :\

I only have a couple things to mention. 1. Make sure your hardware is Server 2008 certified. I am not familiar with AMD based board in 2008. 2. Check the terms of service with your ISP. They likely will require you to have a business account in order to run a web server or mail server off their network. If you don't plan on making the server accessible outside your network, do not worry about it. 3. The Set-up Your Server window is pretty straight forward. If you run into a problem adding roles or features, try only adding one at a time. 4. You can try turning off the Link-Layer Topology options (use GP) on the server and on the workstations (only if they are Vista) to see if it increases your speed.

I've only had moderate success with that method. The reason is likely because it isn't the only reason this behaviour happens. Its funny about this thread really. I removed a fake antivirus program from a friends computer (same OS as yours) and it started doing the same thing. I ended up doing a system recovery on it instead.

That is true. I still get the same error 1. Their error doc has the following info:

Unfortunately, using a WIM file to image an XP machine still doesn't remove the limitations of the HAL. Using a WIM only gives you a file-based structure to store the base image, but it doesn't change the limitations XP has on the HAL. There are some other posts on the unattended XP section on ways to get XP to install on multiple hardware devices, but these are all independent of what imaging software you're using (ultimately, WIM won't help you achieve this). The best implementation of Hal trickery that I have seen so far (concerning WIMs) is TheReasonIFail's: http://www.msfn.org/board/index.php?showtopic=115243

This will be my first official project post thread. In this project, I am attempting to get PassMark's Burn In Test program to work in Windows PE 2.1 x86. Here are the project details: Windows PE: v2.1 x86 (32 bit) Application: BurnInTest v6.0.1002.0 Developer URL: PassMark Software Additional Software Microsoft Process Monitor Heaven Tools PE Explorer (30 day trial, purchase for continued use) This program comes with a plug-in to work in BartPE and Windows PE 1.x environments. Taco Bell has also been working on getting this program to work properly in v2.1. Currently, PassMark is in process of offering official support for this environment. While Taco Bell has been able to get the program to launch properly (using the /x switch), it still fails for me. This thread will be my log of my experiences. The current instructions are to install the program on any computer. Then take the \BurnInTest folder and copy it into the WinPE. The BartPE plugin merely adds an option to launch BIT from its menu. You also need to copy MSVFW32.DLL into \SYSTEM32. After doing this and launching the PE, an attempt to run the program returns the following: and Taco Bell has noted that he had not experienced the Error Number 1 issue. My first step was to run a ProcMon on bit.exe to see what files it uses to and then compare that with what I already had. I had originally run PE Explorer on bit.exe because it has a dependency scanner, however, ProcMon detailed additional dependency files not listed by PE Explorer. The following is the full list of files it uses: Items in normal (black) text were already present in my winpe.wim. Items in Red were not present, and were not present in my VistaBusiness32.wim. Items in Green were not in the PE but were in the Vista WIM. I copied the known files from the Vista WIM into the Winpe.wim and committed the changes. Some things that are noticable: The program uses the process of creating a patch for itself on systems that are not fully supported. This is noticed because it ended up writing into sysmain.sdb, which is the main application compatibility database for Windows. It also (appears) to create make it compatible with XP SP2, as it looks for that file as well. This is only my guess atm. I'm off to test. If anyone has any ideas, let me know. I believe it is safe to ignore the DirectX warning.

Oblivion, aka Elder Scrolls IV: Oblivion, also has an expansion pack which was originally available separately. It is called Shivering Isles. The extra disc may be the additional mods, like Horse Armor, etc. If the box says it comes with those things, then its the right one. Make sure to check for updates once you get it installed.

This is an unfortunate mis-use of terms. Your notebook actually has an SVGA connection. VGA hasn't been used for a very long time. I don't know why the term SVGA isn't used as it should be.

Sorry, my computer at home died and I have been busy at work fixing that (I brought it in) as well as my regular work things. So not much time to be on MSFN this week so far. And yes my reply were to your older posts. Its obvious you and Jaclaz have moved along a lot further since my last contribution, so stay on track with him for now and see where that leads.

BS Explorer, aka BoaSoftware Explorer, is a custom shell created to be used in Windows PE. It appears, based upon a quick glance, that the text (if comparing screenshots on their site) is controlled via bs_explorer.ini. You may try inserting a NULL character into that option, such as ALT+255, and see what that does. Also, when in doubt, try looking for the developer's forum or contact email.

What operating system are you using? Since those were instructions for XP, it is possible the OS you are using has different commands or even registry keys to work with.

I see a lot of posts about people wanting to put the profile on other volumes, and frankly it doesn't make much sense to me. I am presuming its the fact that once the profile gets to a certain size, the OS slows down. My solution to that is to not use the profile for anything that gives me a choice of where to put files.

OK a couple of things to try. Obviously there is a peice missing, and it is likely a dependency. 1. Make sure you are using the files to match your PE type. If using a 32bit PE, use the netsh and dhcpmon.dll from a 32bit Vista machine. 2. On a Vista PC, use Procmon and run your command. Make note of any additional files it is reading, including registry entries. 3. Run depends on netsh and dhcpmon.dll. You may be missing a dependency. I have done very little with getting the PE to do things that aren't documented, but this is always a starting point for me.

Sorry, I'm late to the party Don't worry about the offset that is normal. Examining the MBR.INI we can see the following: Under boot loader, you have "RecoveryPatitionOnStartOfDisk=0". This is because SoftThinks does not follow the best practices for recovery partitions, which is, to put the recovery partition as the beginning of the disk, and the system volume follows it. This is because the recovery partition must be created after the system volume is put on. It automatically splits the disk (it uses a percentage option) and creates a partition to follow the system partition. It then copies the files and compresses them. After this, it resizes the recovery partition to save space. It is easier to do it this way, instead of say, creating a 20GB partition at the start of the drive, and then another one for the rest and install Windows to that part. Its because the SoftThinks software cannot resize the partition if at the beginning, because you cannot change the offset of the system volume once it has been created very easily. Also, for "AskCreateRecoveryPartition=0" if you set this to 1, it would not work unless you had the license key inserted, so don't both trying that one! You may be able to get past this "32byte" error by changing "UseSmallMBR" to 0. OK so you have logs that say that MBR.DLL is running commands, which confirms my estimation. So it may be that their software actually uses Rundll32.exe to execute that command? I was able to restore the F11 functionality using Terrabyte Lab's MBR.EXE. This happens because it could not find the recovery partition. So it loads the next best thing. In my custom project, I got this to happen also. But say I hid the C drive, and tried to load the recovery partition and it wasn't hidden. Then it would do the same thing, except it would try booting off the network, which was next in the boot order. Yes this is an issue with personal equipment. Not everyone that posts here have the ability to constantly redo their theories via imaging, or have the ability to start over once we blow something up. The tool, if run from Windows, would not be able to do a full offset movement, because obviously the volume would be in use! Nah, so I do not think that was the issue.

Welcome to MSFN, varun037! Thanks for the info, atolica! Closing topic, since this is a cross-post. Original topic here: http://www.msfn.org/board/index.php?showtopic=131887

I would recommend re-building the image to be honest. You don't even want to know the headaches you could be facing here if you take into consideration ACLs and Ownerships of files, hidden files and registry keys.

Yes I found that information also. It deals with adding a "custom" resolution, and then reghacking the new keys the cpl creates to make use of resolutions not available by default.

Is the pound character ( # or number sign ) a reserved character? I can't find any full documentation on reserved characters for INFs or Windows.

Slingbox can definately do it, and there are other companies who sell products specifically to do this as well. But a Slingbox is cheaper and Jim Rome likes it!

Verify it isn't DAEMON.EXE, because if so, this is part of Daemon Tools, an ISO mounting program. If you use this program, you should unmount all unmountable volumes before shutting down to see if this issue goes away.

You can use the attrib tool to change the properties. Here are your switches: R = Read Only A = Archive S = System H = Hidden So to make available your standard protected file, use the following: Attrib -R +A -S -H To reverse and set back to how it was before: Attrib +R -A +S +H

Yes a USB key should work also. The Vista PE should automatically detect them, but best if they are plugged in after the PE loads or else they will appear as the C Drive. If you had a USB floppy drive this would also work. That is what we use for those cases.

What packages did you add into your winpe.wim?

Try using the IP of the host instead of the hostname in your UNC path and see if that does anything. Also try to ping the IP address of the server instead of the hostname.