Tripredacus

Not knowing which Operating System you are refering to, an exact answer is impossible. Try reading this to get started or give you an idea. http://www.msfn.org/board/TEXTMODE-MassSto...ive-t19792.html

It is included with the WAIK an/or OPK. Windows Automated Install Kit OEM Pre-Install Kits

I'm confused about the many different programs called GImageX... some of these need to get changed.

I believe that the DOS Window runs at a display resolution allowed by the mode.com program. My LCD (NEC Accusync LCD 72vx) says that the command prompt in Windows 98 at full screen runs at 720x400. This resolution is not supported by your monitor. SeePage 30. http://www.necdisplay.com/cms/documents/Us...als/20WMGX2.pdf I do not know if it is possible to configure what resolution the command prompt displays as.

Are these updates from the Windows Update website? Check the Event Viewer to see if there are any warnings or errors there. Updates usually get logged there. There is also a file you can check for errors. http://support.microsoft.com/kb/902093

uBB does it that way I think.

Its possible with some server-side recoding, but it would be pretty silly to do it just for one guy. Example, View New Posts - nlite and vlite forums.

I sometimes switch to Lo-Fi version and save or print the page.

GHOSTSERVER decided to take a crap yesterday at 14:10. I noticed my VM box wasn't getting an IP (and I needed to test an IP app I wrote) so I checked the server. I hit the button for the KVM but the screen is black. The server is still running (can hear its loudness from under the desk) so maybe it is asleep? Well I press the Ctrl+Alt+Del to see what happens, but it actually started to boot up? The usual DEGRADED welcome screen on the 3Ware came up, and it booted into Windows. The event viewer says that the computer experienced an unexpected shutdown at 14:10 on 10/01/08, but the computer clearly wasn't off when I "rebooted" it today. Anyone know what may have happened? PS: the mouse stopped working on it too... annoying using Event Viewer with the keyboard.

See if you can mount it manually using the PE Tools Command Prompt: imagex /mountrw c:\vistaproject\install.wim 1 c:\mount to unmount imagex /unmount c:\mount to save changes imagex /unmount c:\mount /commit See if these options work or give error. Also make sure you already make c:\mount before you try to mount a WIM into that folder.

That definately looks like a nice tool, but it isn't what I am looking for. I do not wish to reinvent our XP install.

Your hotfixes are located in c:\windows as compressed hidden folders. Example: C:\WINDOWS\$NtUninstallKB925902$

The following keys: http://www.msfn.org/board/Change-individua...nde-t60238.html

Could it be similar to this issue? Do you use automatic logon? http://www.msfn.org/board/Vista-after-logo...rs-t124150.html

Tripredacus has erred.

I figured it was Vista since he says it wanted him to put in a Vista disc.

I am in the market to look at a software solution that will allow us to migrate away from using CD based installs for XP and into a network based option. Currently we use a CD that uses Win PE 2005 to format the disk, load the NIC drivers and download the Configuration Set from our server. After getting the cfgset (default is XP Pro SP2 without additional software) it reads the info from the WINBOM file to connect to the correct distribution share(s) to start the Setup process. I was tasked with the project of seeing how we can get this system to work with the WinPE 2.0, as if I can make it work there, I can modify our existing boot environment to support installs of XP. The problem we are facing is that while the unattend and setup.exe can be called from the WinPE 2.0, we cannot find a way for it to use the WINBOM file as well. Our existing hardware platform is Server 2008 x64, with WDS and PXE-Boot enabled. We can install (Vista) and image (XP and Vista) with this environment but not install XP. I have looked into other options such as BDD2007 but it does not work properly and I cannot find a resolution. I may also be interested in information that allows us to use a PXE Boot Menu. Our system right now boots directly into the WinPE 2.0, but I would like to get a choice between that and say, loading an install from the server. As an example, I have my 2003 server to boot to WinPE or 6 different Vista images, but it never gives me a menu. So any information regarding how to install XP via PXE using a WINBOM file would be helpful.

There is the other reason, some of us like to run different OSes, especially older ones. For example, I still have a notebook at home that runs Windows NT 3.51. Ya it isn't my main computer, its just something to play around with.

Yes you can. It shouldn't cause you any problems anyways. I did a similar thing to my Server 2003 which was installed on the other partition. I left the Program Files folder tho, as some programs will run from there without me reinstalling them.

How did you load up Home Basic without the media to see if they key was in use or not? You can see if you can get a recovery disc from the manufacturer of your computer. Home Basic to Premium costs $80. http://www.microsoft.com/windows/windows-v...e-overview.aspx

The reason for the low specs seems to be because you aren't planning on recording any video are you... I know a couple companies that sell products that do what you want, but without those weird requirements.

You need to run sysprep before you can redploy an image to different hardware. For example, I use: sysprep -generalize -oobe -restart There are other switches, check them all before you decide.

I believe what you are seeing is pxeboot.com. I do not use this config, instead I use wdsnbp.com. They are both located in x:\remote install\boot\x86

Well basically people opt for the unattended solution so you don't have to click through everything. Sure you can make your unattend do all the background stuff and then click through the rest if you wanted to, else just skip all those steps and boot to the install.wim right away with no changes. The Generalize pass does not remove all the drivers. It (may) remove unsigned drivers and (usually) removes the video driver... or to be more exact it reverts it back to "Standard VGA Device". Generalization removes the device specific information that Windows Activation refers to in order to determine if the install has been moved to other hardware. It still will keep most of the drivers for you. One of the big things you will find is that while a bunch of us use WDS, imagex or whatever else, we all use it differently. As an example, I don't use the workbench at all, but I might look into it once I get some free time maybe.

Is this the old question of "my old game doesn't run right" on new Windows? Most reasons are that older games are using a depreciated method of doing something, like sound being choppy, or not working at all, etc. You can fix these things with the Windows Application Compatibility Toolkit. I can't tell you exactly how to do it, as I've only used it once. And that was to get the sound to work properly when running Destruction Derby for DOS. I wish I knew how to use it properly or else I would use it all the time.