Hi,
Originally posted by: amenx
Originally posted by: Nano
So, did anyone manage to sort out the oakcdrom.sys problem yet? Just thought i'd ask.
*Edit*: I myself tried 3rd party boot OSs (eg FreeDos) but to no avail.
GCDROM.SYS is an alternative solution for 965 chipset boards:
http://www.computing.net/dos/wwwboard/forum/16251.html
Thanks - interesting.
GCDROM.SYS seems to work better than SBIDE.SYS.
It's not clear why you need three instances of GCDROM.SYS in config.sys i.e:
DEVICE=GCDROM.SYS /D:cd3 /C0
DEVICE=GCDROM.SYS /D:cd4 /C1
DEVICE=GCDROM.SYS /D:cd5 /C2
but the parameter /C0 (or C1 or c2) seems to address the different mass storage controllers. On my mobo it finds the CDs on C1. Why the SATA controllers are C0 and C2, with the IDE one in between them, eccapes me, and presumably you'd need a C4 if tehre were 6 SATA ports (3 controllers?)
So GCDROM.SYS is more generic, since SBIDE.SYS requires a line like:
DEVICE=SBIDE.SYS /V /D:cd1 /P:1018,10,1010
DEVICE=SBIDE.SYS /V /D:cd2 /P:2018,10,2010
depending on the mobo, and maybe other values might be required.
In addition, SBIDE.SYS hangs if it encounters a controller with two CD attached: Oops.
What a nightmare.
Peter