Tripredacus

I am in the process of setting up a computer using Vista Home Premium 32 bit. The motherboard CD only had a 32bit Vista driver for the audio (although the driver wasn't signed) and the LAN (which I didn't need to install). It did not have a video driver for any version of Vista. I went onto Intel's website and they only provide a Vista Starter 32bit driver for the video. I am wondering if there is any potential problems with using a Vista Starter driver in Home Premium. I understand that Vista Starter is a non-US version with severe limitations when compared to domestic Vista releases. For those who do not know about Starter, check this link: http://en.wikipedia.org/wiki/Windows_Vista_editions

Without knowing which revision you have, presuming it is the newest, this appears to be the driver download. Is this the one you used? http://www.gigabyte.us/Support/Motherboard...amp;FileID=3078 It also seems that there are two Hard Drive Controllers on this board, one for the Intel 82801IR/IO SATA AHCI (ICH9) and one for something else? http://www.gigabyte.us/Products/Motherboar...?ProductID=2636 Where did you download the Intel drivers from? I am actually having difficulty finding a download for them.

1. BCD is how Vista handles booting. In previous versions (like XP or 98) there was a file called boot.ini which informed which partition the operating system was on. You could easily modify this file to add additional operating systems, and then when you booted it would give you a menu (like the menu you see if you try to go to safe mode) and you could choose which operating system you wanted to load. The BCD is just a different method of doing the same thing, but it has more options that you could possibly use that you can't do with just a boot.ini. If you look in the unattended Vista forum, you will find posts about how to use the BCD. I haven't gotten my head around it yet, so I couldn't give you instructions myself. 2. A bootloader is simply a set of instructions for the computer so that it knows what to do after it goes through the BIOS and POST process when you turn it on. The bootloader reads the information in the boot.ini or BCD (or if you aren't using Windows it looks at other files or data) and sees where the operating system is and loads that up. The bootloader isn't a program that you can see like the boot.ini, it is written to a hidden section on the hard-drive called the Master Boot Record, or in another hidden sector or track on the disk. I used this term because XP uses a different bootloader than Vista does. 3. NTLDR is the program within Windows that starts the process of it loading up. For example, Windows doesn't just put up a progress bar and then load the desktop. It does other things like put files in memory, figure out which drivers it needs to load, etc. Invoking NTLDR simply means that the bootloader needs to start Windows up. You may have seen the error "NTLDR is missing" which referrs to that program.

I've had problems with these adapters myself, but not concerning network transfer speed. The problem with this controller (as well as the Realtek 8201 series) is that they are controlled by their firmware in a "software emulation" mode. I am not overly thrilled with hardware's ability to automatically control things, since there are definately instances where being able to have hard settings would be better. Anyways, my problem with these controllers is that Ghost does not recognise them at all, and before the days of us using PXE to image machines, this was a real big problem.

If you look at the script it made for you, and recreate what it is doing, you can learn to read what exactly the recorder code is. Then you can remove the extra lines of code that aren't required for your application. EDIT: I made a script using the recorded once, but with a resolution detection. While the program supported multiple resolutions, the management at the company the software was for couldn't rule out the possibility of having rogue resolutions on their machine, so I had to scrap the entire idea of basing it on mouse control. If you have the ability to script it totally using keyboard only controls, then I would recommend you do it that way.

That way may work if you are only building an image for the machine you are capturing from. Otherwise, you are going to want to do a sysprep, else after you deploy, Vista won't start with the "hardware has changed" message.

I notice that you use quotes in some places but not others. Typically, choose one method or the other (using quotes or not using quotes) and don't mix and match like that. Also, is it normal to have a wildcard after adminpassword?

Try running a scandisk and/or defrag while in Audit mode before you sysprep.

Which Intel board is it?

THe boot manager isn't something you can see in/as a folder. So did Vista actually get installed on the same partition as XP? If not, you can edit your BCD so you can dual boot or use a different bootloader.

Well the parts were taken to build a new more compatible 2008 server, except that this project is being transferred to someone else too. I think I'll still get to manage WDS on it once it is up and running but who knows.

I only install things I need, not go about and install everything just because I can. I do seem to be the only person I know who operates their computer this way, and I am also the only person I know that hasn't had to reformat their OS HDD ever.

Well here's some bad news... Cluberti might better understand this situation. See the original plan was for me to create a test server, then a second server for production was going to be built. In fact, we had already gotten in the parts for the new server, sans (no pun intended) the hard drives. An executive decision was made and in order to save on the system costs (we are getting one next to nothing after we requested eval products from Intel) they would take the hard drives in my test server. So basically the powers that be have scrubbed my project. They are taking the chassis, one of the RAID controllers, all 8 HDDs and the PSU, and MAYBE the CPUs from my project so I'm basically up the river without a paddle. Thanks a lot for all of your help and input! I am sure I may dream up another project to make a thread about in the future!

Was it re-authorize the DHCP server to refresh the records on it Well I am thinking that it is getting this error because DHCP on UNCLESOCKS is disabled, and I am authorizing the legacy to run DHCP instead. I did it this way because I couldn't get any computers to boot via PXE with DHCP and WDS running on the same computer.

Indeed this is enabled. What is that service used for specifically? When I installed DNS, it turned that on as well, or perhaps it was already running before the machine was given to me for testing...

Hey check your power supply!

Partition Magic has the ability to create a bootable CD or floppy disk set. That way you can boot into Partition Magic and it doesn't have to be on the Hard Drive.

Here's an update, as I have fixed my problem with a work-around. I contacted Apple Support and they recommended connecting it to a Mac to downgrade the firmware. They said that this would allow it to work with previous versions again. I called up my cousin because she had a Mac, and to get it taken care of. It turned out she also had the older iTunes installed, and when she tried to update it, she was told her MacOS was out of date. So that idea went out of the window. She recommended I take it to the Apple Store and have them downgrade it. Well, the guy (Mac Genius) at the Apple Store evidently are not of the same mental capacity as Apple Tech Support. They reset it for me, but said that it would still only work in an iTunes 7.6 software, because the firmware does not dictate the software version required, but the "software" that is installed on the iPod itself. I was pretty bummed at this point. So I downloaded the SP2 redist, and was about to install it when... I just wanted to try spoofing the service pack again. So I connected up the iPod when suddenly... WINAMP DETECTED IT! Here's how that happened. A couple days before, I tried out the new Winamp version. I did not like it because it was really slow compared to the older version when it came to ffwding within tracks, and there was a pause when crossfade was enabled. So I had uninstalled it and reinstalled the older version. Well even though the older version did not have iPod support, the uninstall for the new version must not have removed all of the components. So the old Winamp detected the iPod plug-in, and thus the iPod. It was also able to erase and copy songs to it. My last step was to uninstall the iPod updater, iTunes and the Apple Updater. The best part is that Winamp can also copy album art to the iPod as well, and the sync time seems to be faster. So once again I've managed to NOT have to install any service packs to get something to work.

It is formatted FAT32, and appears as a EISA partition in Disk Administrator, without a drive letter. I also tried the other application on that site, MBRWORK, which appeared (at first) to be a hopeful fix. My test computer (where I am doing the MBR work) is a clone of computers that we currently image daily. So I have ready access to production units. I captured the MBR off one of the working production units, and then applied it to my test computer. It went through without error, and displays the appropriate information on the screen during boot-up. However, it did not respond to the "R" key and the "F10" key did not seem to work any better than before.

This program did indeed give the ability to get a keystroke from the user while displaying information on the screen. However it would not boot the recovery partition I use. It is a hidden, no drive letter 0x12 partition that IS bootable. Except when I press F10 (instead of F12) it tried to boot off the network. I disabled network boot in the BIOS and it will then say "No Bootable Device"... So it seems that the MBR.EXE is looking for a different type of hidden partition than the one I am using.

http://www.microsoft.com/windowsserver2008...icalInformationYou need Xeons running Intel's VT from this list (Select "Intel Virtualization Technology" from the "Supported Features" list and click the "Filter on Selections" button). I am not sure if it's a guarantee that everything on that list will work, but it's for sure anything not on that list isn't . Perhaps there is something I need to enable in the BIOS, or install from Intel's website so Windows sees that it is capable of running it. We are going to need to use Hyper-V to support our legacy customers (ie those who require 16bit Ghost to be used). This would be an excellant time to look into Microsoft Deployment ToolKit. Using this and the MultiCast Feature in 2008 you could image all your laptops in a relatively short time I am already using that, but we can only use the deployment features provided by the OPK toolkit, not the "corporate" toolkit. Right now, these notebooks can image in 3 minutes using the 2003 WDS. So with this relatively short image time, it is not a problem to do one at a time, since we don't get that many orders for that notebook model at once. But, using WDS on the 2003 for production is not the original idea, its just that some network controllers (software controlled like Broadcom57 and Realtek 8111B) do not work with our current imaging system. In other news, the 2003 server started acting up ever since I joined GEARS to the domain. It now sees our legacy server as being a 'rogue' DHCP server, even tho it is available as a managed DHCP Server in UNCLESOCKS' DHCP management control panel.

Simple File Sharing does not change how security works in Windows, it just changes how you can see and interact with it and its settings.

I have similar experiences with our corporate Anti-virus. It likes to detect my programming tools as 'trojans' and 'hack tools' and tries to erase them from my hard drive and our network drives. In my case, there doesn't seem to be an option to make it ignore those things...

Im not sure about converting a Vista, but it should work if you create a generalized sysprep image of it, then inject the driver? But is there a specific reason you want to use AHCI instead of IDE?

I am not sure if Ghost can manually do this for you, but to make a bootable CD/DVD (I used a DVD) you make it similar to a floppy boot disk. And make an ISO using oscdimg and use the -m command, and also use the appropriate bootloader. Or just make a WinPE CD and put Ghost32 on it, and the image. I don't see why a floppy is required.