Ascii2

Yes, it support USB boot but from HD or other devices but flash USB not working so that i'm looking for update for my BIOS. The Gigabyte BIOS also supports "Boot other device" but its interface to change its setting is disabled and its default value is "Disabled". The "Boot other device" may be enabled by modifying the flash BIOS file.To boot to the flash drive, the flash drive should be partitioned like a hard disk with its boot sector written to launch an operating system usually DOS or a variant) from the flash drive.

I wish to update the Microcode Update Device driver (update.sys) on Windows 2000 family operating systems. The "update.sys" file contains microcode that is uploaded to Intel processors on performance of function of the update.sys driver. The newest update.sys file I have found comes with Windows XP Service Pack 3 (may be acquired http://www.microsoft.com/downloads/info.as...SP3-x86-ENU.exe ). I have attached images to this thread: One showing "Microcode Update Device" in device manager, and the other a search of the Windows XP Service Pack 3 files for "update.sys" contained within the files. For the search for the text "update.sys" of the Windows XP Service Pack 3 files, I had decompressed the compressed files to the search's root directory ("xp_sp3") and extracted the cabbed files to other directories. No cabbed files had references to update.sys. The only reference to update.sys from the expanded (decompressed) files was for the "wuapi.dl_" file. The file "update.sy_" is the compressed update.sys file and is located in the i386 directory. I have the driver file from Windows XP Service Pack 3, update.sys, containing the newer microcode updates, but I do not have the a Setup Information file (*.inf file) for the installation of the driver. I request assistance for this matter to prepare a driver update. Any help in this matter is appreciated. EDIT: I would attach the "update.sys" file to this thread, but it appears the file is larger than the limitation by the forum (even in compressed form).

I checked the Gigagbyte F7d BIOS and have determined that it should support USB boot devices (where the boot order is selected).

The quoted information is not accurate.

Indeed for a version of QuickTime Alternative earlier than 1.90 (although the DirectShow filters of versions earlier than 1.90 did not work well).

The following is an excerpt from Microsoft Windows Media Player 6.4 help documentation copied from a computer running Windows 2000 Professional with Service Pack 4. The help documentation makes reference to Windows Media Player supporting Apple QuickTime and QuickTime file extensions.Does Windows Media Player 6.4 come with QuickTime support? I have not been able to get QuickTime files to play in Windows Media Player 6.4.

Or that the media for which problems were encountered is not correctly supported in firmware.

As DonDamm mentioned the problem may be bad RAM. Alternately, the RAM may be file but a related problem may exist (like slightly conductive dirt material shorting circuit).The problem may also be a bad driver (not necessarily corrupt). If a corrupt driver is run, undesired behavior may occur. Some drivers from the Windows XP installation source do not correctly run the hardware they are meant to implement. Try removing PCI and ISA cards (except Video if it is being used), and see if the installation finishes. Another possibility is a bad or inadequate Power Supply.

IE was not open when I attempted to change the settings.Also, I forgot to mention that the change using the VBscript was observable immediately in the Internet Properties box after the running of the script (but not open when script run). I have rebooted like nine times after I last posted, installed Microsoft mouse software (with driver), and a newer version of my chipset (nVidia nForce4 SLI) drivers. I am now able to make the changes in the Registry Editor and immediately observe the changes in the Internet Properties dialog box (although I do not know why I was not able to before).

I believe I now understand the different meanings of the values for the "Flag" DWORD. I tried to apply different values for "Flags" in both HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER hives using REGEDIT on Windows 2000 Professional with Service Pack 4. After apply the values, I could not observe changes in behavior of the display in the Internet Properties dialog box, even after restarting Windows. After using a VBS script to apply the changes to the "Flags" values, the changes in behavior of the display in the Internet Properties dialog box were observable immediately. Why was the VBS script able to change Internet Security behavior, but changing the "Flags" values in the Registry Editor did not?

At HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\0 and HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\0, exist DWORD values "Flags". I have found different sources using different values for the "Flags" DWORD. Some sources: http://support.microsoft.com/kb/182569/ http://antionline.com/showthread.php?t=237895 http://surfthenetsafely.com/ieseczone3.htm Although, a Microsoft Corporation article is one of the sources, other sources use other values for "Flags" that are not documented in the Microsoft Knowledgebase article. What are the valid values for "Flags" and what effect do they have? Relevant operating systems: Windows 2000, XP, and Server 2003 families

What is the hardware ID of the device?

I leave a note for those using FlashGet 1.73 and arrive at this thread. This does not apply to earlier versions of FlashGet. I would recommend removing the GetIt module that the FlashGet installer registers. The GetIt module is used to give an interface to acquire SWF file URLs to pass to FlasgGet 1.73. The GetIt module often causes problems, especially in Windows 2000 family operating systems, resulting in Internet Explorer crashing. Wherefore I recommend running (or including in batch) the following command: regsvr32 /u /s "%SYSTEMDRIVE%\Program Files\FlashGet\getflash.dll" Unregistering the GetIt module will cause monitoring of SWF files by FlashGet to cease.

< EDIT > No serial needed (I just used my old serial and it worked). Thanks to benners and dobbelina reporting it's now free < ADDED > FlashGet ToolBar is removed, too. Thanks mazin, I found your post quite useful.

I found the setcommand.inf. Thanks jaclaz.

The environmental variables do not seem to apply to Widows 2000 Recovery Console (I tested it). The "set" command, once enabled, however is able to set the variables to remove restrictions.I would like to not have to type the "set" commands every time I want to use a locally installed Recovery Console unrestricted. I have tried using an "AUTOEXEC.BAT" file at the root of the bootable partition with the set commands, but it failed. Can this be done without using the floppy drive?

No. It is not there. Clicking the link yeilds a "The page cannot be displayed" page.

Your probably have your system drive connected to an SATA controller as part of the motherboard's chipset.EDIT: I looked at the specifications of the Asus A8V and it appears that chipset includes two SATA controllers. The problem wherefore may be BIOS. The controller being used may be disabled or not implemented in BIOS. If the later, a different BIOS, floppy drive, or an SATA to something else adapter may be necessary.

Put the SATA controller driver on a floppy. Then try setup again, insert the floppy, and tap F6 when prompted. Windows setup checks only the floppy drive for the driver.

Where is the pre-made .inf file?

I have been trying to find information on how to allow all paths, wildcards, and full write access to Windows 2000 Recovery Console or Windows XP Recovery Console. Registry keys and values I have found that I believe may be relevant are: At HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SeCEdit\Reg Values\MACHINE/Software/Microsoft/Windows NT/CurrentVersion/Setup/RecoveryConsole/SetCommand two DWORD values exist, "ValueType" and "DisplayType". At HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Setup\RecoveryConsole exists DWORD values "SecurityLevel" and "SetCommand".Which values should be changed to allow all paths, wildcards, and full write access to Windows 2000 Recovery Console or Windows XP Recovery Console? The operating systems of relevance are Windows 2000 family, Windows XP Professional, and the recovery consoles for both Windows 2000 family and Windows XP Professional.

How can what Windows Registry keys and values are checked by an installer at running or slightly after running an installer be determined?

I have recently used nLite 1.3.5 to integrate updates into my Windows 2000 Professional with Service Pack 4 source. I then proceeded to install the nLited Windows 2000 with Service Pack 4. Everything seemed to go well except for an appearence of the message "Disk I/O Error: Status = Disk I/O Error: Status = 00000000" during Windows setup (before tapping "F8" to agree to terms I believe), and prior to each boot of Windows, even Safe Mode. Why does the message appear and how do I stop it from occuring?

That would probably work, but would be far from ideal; much disk space would be required (posilbly per computer).Why does Windows Installer launch Office 2000 setup prompt for intallation source after suposidly completely installing Microsoft Office 2000, for accounts that had previously not used Office? I was thinking, perhaps an Office unattended install (if possible) may yeild desired results.

Is the forum baffled by this?