Tripredacus

Try to change ownership on that folder to your account.

This looks like a good project, just one request, your images are very large. Change your images to use thumbnail links.

I posed this question to someone else, he said "make a boat out of the trees" and I told him he had no tools. He said "Tom Hanks didn't have tools in Cast Away". I thought Robinson Crusoe was a better idea.

Ethan, is this related to this thread? http://www.msfn.org/board/domain-name-t143083.html

As far as notebooks go, I wouldn't really want one that only has Intel graphics controller. Especially if they are going to call themselves Voodoo!

I see this happens a lot on notebooks, where they cannot even read the CD-Rom that comes with them. However I believe it is OS related in some way, as for example they can boot off CDs. I do not know the solution to this problem.

This is saying you have a problem with your XML. Please edit your autounattend.xml to remove the product key and attach it to your reply. We can look at it and find the problem.

sfc /scannow Make sure to create a restore point before running it. Sometimes running this program when malware is present, it may damage your Windows. I typically do not like running this program.

This reminds me of the olden day of playing D&D and now Gamehead is the Dungeon Master, and I'm in crazy world trying to figure out how I can get the sharks to save me from the fire.

This topic might get more views in the XP Unattend forum (where topics like this belong)

Yes well we went this way because of learning the hard way. Part of it is because of left-over imaging policies when there were multiple HALs and non-ACPI compliant hardware. The real deal breaker for us was when HP blew up a bunch of their Intel chipset machines by using a single image that would write in an AMD file and blow up Windows after certain updates were ran. We decided to play it safe and not want to end up with that kind of support nightmare! All it meant for me was that I ended up taking on new responsibilities and end up from a worker type position to a management type position.

Yes it could be possible that the MSI file extension is registered to open MSIEXEC but maybe that program is missing or corrupted. In that same vein, it could be that a dependency is missing that the program needs.

I'm fairly certain that you won't be able to activate using the key on the COA. Home Basic might work differently, worst case scenario you may have to call the Activation phone number.

Well this is borderline networking related, however best fit in Software forum.

What is the full filename for the item you are trying to open?

Mine is slightly different, maybe it helps? and mine from Nero8 I added the last one in case those different switches work with Nero9.

Back in the later days of 72-pin SIMMs there were systems that required them to be installed in pairs so using sticks in pairs has been around much longer than RAMBUS. RAMBUS was just the first one to optimize how they worked in pairs...at the desktop level. Servers have also required memory be installed in pairs (and sometimes quads) for quite some time. The ServerWorks chipset in his server will actually using "memory interleaving" (aka dual-channel). It sucks that Broadcom let ServerWorks drop off after they bought them because they used to make some awesome chipsets...even if their PATA controllers sucked (you were generally using SCSI based drives on them anyway so that didn't matter). Using multiple DIMMs at the desktop level is another case of server technologies trickling down. This always happens. Look at the number of consumer-level motherboards that come with integrated RAID now days. That is true. Some of the Intel Workstation boards and Elite series (gamer type) boards now have memory options that came straight from RAID technology. So now you can set your memory up in RAID arrays too. I imagine someday desktop boards will get this option as well.

I am wondering if winpeshl.ini does not like the > character. Try having winpeshl.ini run a .cmd file instead, and put your diskpart command in that file instead. Make sure you don't make it exit, or have winpeshl.ini run something after the .cmd so the PE doesn't exit and reboot on you, like have it open notepad after it runs the script, so then you can check it.

While the host requirements for WinPE 3.0 x64 is 512MB RAM, running applications in it may not function unless you have 1GB RAM. WinPE 3.0 x86 works fine with a minimum of 512MB.

There is no harm injecting the drivers into the WIM because Windows is still going to use PNP to install them. Setup will NOT install drivers for devices that are not present, if this was your concern. Yes you can only generalize an image 3 times, but in my experience, Sysprep is likely to complain on the third time, not the fourth. So far I've never had to use skipReArm in the registry yet. The images I store have 1 generalize on them, so they can survive a second. I have 1 custom image that has 2 generalize done on it, so it can't be done again. If there is something totally wrong with that one, I'd have to recreate it. That doesn't take too long, I've done it 3 times already. As far as your "updates" go, you have a couple options. You can specify commands in your sysprep.xml that run files or programs from a network share. You can have it run this during OOBE pass or setupComplete. This way in order to change what you are installing, you change it on the share and not the image. I'm pretty certain that one of the generalize phases gets used up during installation.

I'd be interested to know if you asked the site owners or bensam about doing that before you had.

There are 2 stickied posts in this section, different ways to handle this. I have not used any of them, here are the links: http://www.msfn.org/board/7liite-t142382.html http://www.msfn.org/board/7customizer-replacement-vlite-windows-t139077.html

OK since either you replied to the wrong topic or these two issues are related. I merged your two topics into one. Which account did you delete? The hidden Administrator account?

Has a BIOS update been run on the computer? If you got this from a Sony Authorized Retailer, this would mean that you are still within the warranty period. You should go through their tech support so that you do not do something (like the things we may suggest or point you towards) that will void your warranty.

There are a couple things I can see. One is a security option: Interactive Logon: Require Domain Controller authentication to unlock workstation This by default in 7 Pro is disabled. This might fix that problem of the admin accounts not being able to log a user off.