Results 1 to 4 of 4
DVD is iso9660, files are correctly copied. my new SATA DVD R/W drive is not being detected in the BIOS, but is being detected by Linux. All I need it ...
- 06-30-2008 #1Linux Newbie
- Join Date
- Apr 2005
- Location
- West Oz
- Posts
- 140
SuSe 11.0 DVD - no start
DVD is iso9660, files are correctly copied. my new SATA DVD R/W drive is not being detected in the BIOS, but is being detected by Linux. All I need it to set it going whilst in linux and I believe it will be ok. I have autorun.inf, an .exe file and another file which is represented by a gear as the only files that might fire it up. There are several other files visible. There doesn't appear to be a .iso file as such, but My Computer identifies it as an iso file structure. I can't detect the drive in win98SE/MS-DOS. I have 2 x IDEE HDD's and a floppy. I do not know how to start it using a bash command. Any ideas pls?
2.6GHz Celeron, 1GB, 160GB, 128Mb SuSe11.2; PCTV, GBit eth0 on P4PE, 10/100 eth1 <Ride to ride again>.
- 06-30-2008 #2
Every thing sounds correct except that the BIOS will not boot to the DVD drive

You will not see the Linux file system in Windows. Windows is not smart enough
Try running the EXE, 11 is supposed to be installable from Windows.
- 06-30-2008 #3Linux Newbie
- Join Date
- Apr 2005
- Location
- West Oz
- Posts
- 140
sorry, windows does not see DVD drive at all, cannot use it. Need to access DVD from Linux, by command line or some part of GUI. Trying to sort mbrd BIOS and SATA/RAID config, but not readily avail. fix file is M$, 2.4MB, which I can't run in a FDD or as a CD at boot. I'll look again at its extension, it might run under DOS after boot from HDD???????
2.6GHz Celeron, 1GB, 160GB, 128Mb SuSe11.2; PCTV, GBit eth0 on P4PE, 10/100 eth1 <Ride to ride again>.
- 06-30-2008 #4Linux Newbie
- Join Date
- Apr 2005
- Location
- West Oz
- Posts
- 140
Pls ignore these posts, my hardware in incompatible, I now discover.
2.6GHz Celeron, 1GB, 160GB, 128Mb SuSe11.2; PCTV, GBit eth0 on P4PE, 10/100 eth1 <Ride to ride again>.


Reply With Quote