Tripredacus

Yes I suspect a lot of people are getting the Driver Error, but every time the action still goes through. I've seen it in various cases of interacting with the database, be it posting a reply, moving a thread or...

Here is the location of the complete system memory dump. https://skydrive.live.com/redir?resid=DF9CED75545B2B97!215&authkey=!ADu8Jw2EiojvJqc

A switch box would be enough to isolate them. You can pick them up relatively cheap.

You may be able to access Windows XP Russian version on Technet or MSDN.

At least some version of the official Mame works on Windows 98 without Kex. I have some old version on mine, no Kex, and actually its Win98FE. That PC isn't hooked up so I can't say what exact version is on there.

I agree that Developers should have it as well. We will have to wait for Xper to set it up if he thinks its a good idea too.

Take a look here:

Based on your description, it would make sense that the failure is in specialize somewhere. I think at the point you get that error (in your screenshot) you should be able to open a command prompt (SHIFT+F10) and be able to find the setupact.log and setuperr.log that may have more information. Regarding the XML file you attached, the only thing I can see regarding language is that you aren't using the proper code for InputLocale. Try using 0c09:00000409 (en-AU) and 0409:00000409 (en-US) instead.

Some things to note based on your autounattend.xml... - No need to specify the Administrator account as the one that logs on automatically. It does this anyways. - I see you did not create any users in AuditSystem. This implies that you will be using the built-in Administrator account, but unfortunately this won't work because the Administrator account is disabled! - I would take all those commands 1-12 and put them in a .cmd file. Then just call the CMD file. I think you should have some error handling present so that you only run Sysprep if you can confirm all your commands ran. BUT there is still a problem with this as is. You sysprep command at 99 would fail because sysprep will already be running. If you wanted to run sysprep with the answer file, you'll need to kill the one that's open already. You can use taskkill in your CMD to do this. I have no idea what you are doing with that command in specialize... Here is an example unattend I had used for testing. <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="auditSystem"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <AutoLogon> <Enabled>true</Enabled> <LogonCount>1</LogonCount> <Username>Admin</Username> </AutoLogon> <UserAccounts> <LocalAccounts> <LocalAccount wcm:action="add"> <Password> <Value></Value> <PlainText>true</PlainText> </Password> <Group>Administrators</Group> <Name>Admin</Name> </LocalAccount> </LocalAccounts> </UserAccounts> </component> </settings> <settings pass="auditUser"> <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Order>400</Order> <Path>cmd /C start /wait %systemdrive%\temp\setup.cmd</Path> <WillReboot>Never</WillReboot> </RunSynchronousCommand> </RunSynchronous> </component> </settings> </unattend>

Duplicate post, see:

I made one AutoIT exe once to prompt for a password (allow access to cmd.exe when using winpeshl.ini) so maybe it can help you. $GUI = GUICreate("Login",210,80,-1,-1,0x16C80000,0x00000181) $USERNAME = GUICtrlCreateInput("Username",5,5,200,20,0x01) $PASSWORD = GUICtrlCreateInput("Password",5,30,200,20,0x21) $LOGIN = GUICtrlCreateButton("Login",50,55,100,20) GUISetState(@SW_SHOW,$GUI) While 1 $MSG = GUIGetMsg() If $MSG = $LOGIN Then If GUICtrlRead($USERNAME) == "USERNAME" And GUICtrlRead($PASSWORD) == "PASSWORD" Then Run(@Comspec & " /c cmd.exe") Exit Else MsgBox(0,"Login","Incorrect username or password.") EndIf ElseIf $MSG = -3 Then Exit EndIf WEnd Exit

If you try using this on WinPE4 x64 and do a UEFI boot via CD/DVD or PXE (or whatever) you'll find that everything is thrown off regarding pictures and text size. This is because WinPE4 can detect the native resolution of the display and will use GOP mode to automatically set the resolution. I have just tested a method of using ZOOM in javascript in a test HTA that you can use in this case. Add the following Javascript code to a script element. I placed mine after the Script end tag for the VBScript code. <script TYPE="text/javascript"> function pageLoadFunctions() { document.body.style.zoom = screen.height / 768; } </SCRIPT> Then I change the BODY tag: <BODY ONLOAD="pageLoadFunctions()"> It isn't 100% perfect, the right side of the HTA's background image is cut off but overall it is better. Edit: This works fine on a 4:3 display. It leaves a large white space on the right side if using a 16:9 display and 1024x768. This is caused by the wallpaper background image.

What did you do to make the Win7 one work? All the info I can find about this error has to do with the hard disk size/not enough free space. http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_install/windows-7-starter-install-error-code-0x80ff0000/e2c3f49e-71c5-44ed-bb71-ae42aa2eefbb

I fixed the post. I didn't see any errors in there and the only warning was complaining about not being able to set the language. So.... what was done different now that you did the install?

I wonder if there is a setupact.log still available on the PC that Windows 8 used. Can you search for this file and fine one with a date/time that matches the time you tried to install Windows 8?

I assume you're referring to RT, right? We can still do useful things on "regular" Windows 8. I don't actively "use" Windows 8, so my experience with it is in a stock form... nothing is installed. So it booting to the desktop seems pointless to me.

I found another peice of hardware where it doesn't work. I configured the OS for bugcheck but the key presses aren't working. The computer is not locked up, as I can go about doing anything else except initiate the bugcheck or use Media Player.... Also on this particular PC, the CD drive can never read an audio CD in Explorer if an audio CD is in the drive when computer boots or reboots. If I take the CD out (with Media Player still in hung state) and put a DVD in, it is read and accessible from Explorer. Data CDs work fine also. I'll try another system to see if I can get it to bugcheck.

This whole "can boot to the desktop" is really deceiving and potentially useless. This is because there is nothing to do on the desktop except open IE or Library. Might as well keep that Start Screen to show up by default, because without a Start Menu, what's the point?

The example you quoted has an equivalent in AutoIT known as StringRegExpReplace which has this description: Replace text in a string based on regular expressions http://www.autoitscript.com/autoit3/docs/functions/StringRegExpReplace.htm Now even though I did read that link I had originally posted, I am not certain as to what language it is in exactly. Here are the basic concepts of RegExp: http://en.wikipedia.org/wiki/Regular_expression#Basic_concepts Here is W3school's Javascript page: http://www.w3schools.com/jsref/jsref_obj_regexp.asp

Here is an example of FirstLogonCommands that runs powercfg.

Welcome to the MSFN!

When UEFI 2.3.1 spec was being "shopped" originally during the Vista days, the consensus was that it should only support 64bit architecture, as they expected 32bit to be long gone by the time it got adopted into the "desktop" space. By "they" it included the members of the UEFI working group (Microsoft, Intel, etc) and other manufacturers. So no formal development was made by anyone (officially) for x86 on modern UEFI... If you recall originally that Windows 8 was only supposed to be available in 64bit and 128bit but evidently the world just wasn't quite ready to let go of x86. So to put it mildly, x86 is not designed to boot in UEFI mode... but also MS did not design Windows 98 to last into 2013 so anything's possible.

Something definately was changed. I can't say exactly. I think the "XML" is the same as Windows 7 but not Vista, but I have found that Imagex does not deploy a Windows 8 image properly 100% of the time. But DISM works fine. That's all I can tell you about that but I bet its related.

Yeah it has something to do with needing to show one of the pages in OOBE, you need to omit either the AccountName or ComputerName (I forget which). I usually get around this by deploying an image to Audit Mode. Creating a user account, assigning a picture to it, then sysprep with an answer file. I obviously create an account with that answer file, but I set the pre-created account as the one that logs in automatically.