Problem booting from external DVD writer on Gigabyte DS3

[jimw428]

Try this. Put your MB driver CD in another computer and try and open it. If you can go to DRIVERS. The USB drivers for your MB are on the MB CD. You will be instructed to get a USB driver from Microsoft.

I am sorry but I have to say it: badge, you didn’t understand my problem. I don't have any problem with the USB controller in windows, and all the drivers on the motherboard cd are for windows. You see, there is no concept of driver outside the boundaries of a kernel, and the thing is I am even trying to load a kernel! This kernel can be windows or linux or minix or whatever.

I think that indeed this is a BIOS problem and I will try to contact people from Gigabyte to get some support. In any case, if any of you have found a solution in the mean time, it will be greatly appreciated!

Trust me, this is NOT a BIOS problem. Here is a basic requirement you're overlooking.

Here's What You Need to Use Windows XP Professional

• PC with 300 megahertz or higher processor clock speed recommended; 233 MHz minimum required (single or dual processor system);* Intel Pentium/Celeron family, or AMD K6/Athlon/Duron family, or compatible processor recommended

• 128 megabytes (MB) of RAM or higher recommended (64 MB minimum supported; may limit performance and some features)

• 1.5 gigabytes (GB) of available hard disk space*

• Super VGA (800 x 600) or higher-resolution video adapter and monitor

• CD-ROM or DVD drive
• Keyboard and Microsoft Mouse or compatible pointing device

Note that there is no mention of a bootable USB device. Be mindful of the potential device compability issues relating to the creation date of your WIN installation CD. This is why the WIN install will search for updates very early in the installation.

You should understand that BIOS (Basic Input Output System) is simply what the name implies. It provides the very basic interface code to support a given feature, Just because it indicates USB support doesn't mean it provides supporting code for all possible USB attached devices. That's what device drivers are for and they can't load until the OS install begins, and depending on the OS creation date, the specific driver may not be present.

Do your self a favor, buy a cheap CD/ROM IDE drive and install it, so you meet the min. configuration requirements of Windows. Your problems will all go away and you won't need to RMA anything.

 

[Batspoon]

Is really that hard for you two (badge and Jimw428) to understand that most current motherboards emulate mostly ANY Universal Mass Storage device connected to the USB hub to act just like an ide or sata controller does ???

And it happens that because the emulation code is stored in a PCI Option ROM module in the BIOS or even integrated as part of the BIOS core in some motherboards, is very likely that the actual issue has something to do with a buggy BIOS release or an incompatibility between the usb controller in the external enclosure and the emulation code in the bios.

 

[jimw428]

Nonsense! If the code is stored in a "PCI ROM" how does it get updated when necessary? (ROM=Read Only Memory) Admit it, you really don't understand how this works, do you?

 

[Batspoon]

Nonsense! If the code is stored in a "PCI ROM" how does it get updated when necessary? (ROM=Read Only Memory) Admit it, you really don't understand how this works, do you?

I knew it was going to confuse you :lol:

PCI Option ROM, it's just a module name commonly used in AMIBIOSes to hold the pnp drivers for onboard devices like the Remote Network Boot via PXE, the RAID controller firmware and in some cases the USB Legacy Support too. They reside in the same EEPROM chip as the BIOS firmware does simply because they are part of it. I know what a ROM is you tool... I also said that in some bioses the code is written in the bios runtime core.


I really think you need to get yourself updated... BIOS firmwares aren't like they used to be anymore... and really these aren't news at all, not a new feature only found in AM2 and Core2Duo supporting motherboards.

 

[bogdancoder]

Just to clarify things: I am trying to install come Linux distributions that I have on DVDs, and not Windows.

Secondly, the boot sequence (that you actually set in BIOS) is not in any way affected by the OS. Furthermore, the bios actually detects the device. It prints Storage Device Detected: Plextor PX 740A 1.02. So in the end it is a BIOS problem (if not a problem generated by the device's firmware... It is the latest (1.02) but still...)

I already contacted Gigabyte and I am waiting for a reply. When I receive it I will post it here.