Mateusz Viste schreef op 21-7-2013 18:45: > Just like Rugxulo, I'm a bit lost about all these IDE/SATA/PATA stuff, > until now I was naively assuming that a SATA CD drive is behaving like a > PATA one, and same drivers will work, and the only difference is at the > physical level...
You're right. IDE can be configured as PIO or UDMA, SATA can be configured in AHCI or IDE (legacy) mode. That still doesn't take into account other interfaces/controllers: * SCSI * FireWire * USB * parallel port * serial port * soundcards * specific interface cards All of these can have a CD drive attached to them. Remember Iomega's zipdrives having lots of different drivers > By the way, how come that SATA HDD drives works fine without requiring > any additional drivers then? Ancient BIOS int13 compatibility causes your bootdrive to be listed as drive 0x80, and DOS kernel assigns driveletters to partitions on it, starting with C:. Same as some small capacity removable drives (ZIP, USBstick) could be listed as drive A: , and high capacity ones as drive C: > Anyway, I tried to replace the xcdrom.sys with udvd2.sys, as I > understand that the latter have some special magic for supporting SATA > CD drives, but unfortunately I got some troubles - when UDVD2 loads, it > freezes the boot for ~1 minute, which is really a pain. Ouch, thought this was solved, both with and without some custom fixing driver. Most recent VirtualBox (4.2.16?) used? Most recent UDVD2.SYS used? http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/cdrom/uide/drivers-2013-04-30.zip In worst case, revert to XCDROM but keep UDVD2 around. Also add SYSLINUX's ELTORITO.SYS driver on the disk if you want. That one is very specific though, and only grants access to the most recent ISO9660 filesystem that you booted from in non-emulation mode (as used by Isolinux and GRUB). Thus only grants access to 1 'cd-drive' no matter what interface you booted it from. (but even that can be broken, if replacing BIOS USB emulation stack by an own USB driver stack in DOS). Your CD is in floppy-emulation mode however, trying to explain how to add isolinux is a slight nightmare though, same for trying to explain how to make it bootable. > I am testing this inside a VirtualBox machine. I recall some months ago > (or was it years maybe?) some flames on the list about this problem, but > don't remember much constructive ideas, other than saying 'virtualbox is > buggy'. Incomplete emulation isn't much fun. Every emulator has its own quircks. > Is the situation still the same, ie. is there no way to make UDVD start > faster under VirtualBox? Is there any other driver nowaday that could > handle IDE/SATA drives and not freeze VBox for a minute? Keep what you have if that proves to be better. Ideal loading order would be: 1) ELTORITO.SYS 2) if fails, load XCDROM > Of course I don't say UDVD2 is bad (and I certainly don't want to start > any nuclear war about this), but the fact is that many people test stuff > under VBox these days, and if a bootable CD freezes 2s after starting > booting, they won't get any further. You're right. I've not tried to use RUFUS on your ISO to get its content onto USB flash drive. A step too far for now :) Bernd ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
