This is not an issue, but a question and since you don't have a Discussions section, I'll just go through here. I'm interested in possibly using xroar for my coco emulations instead of mame. I rarely emulate the coco, but it seems that almost every time I try in mame, they've changed the requirements, especially for floppies and get more restrictive all the time. I had this statement in my coco3 config: "ext:fdcv11:wd17xx:0 525qd" and now it seems that it won't accept this. It also seems to view a ds-40t floppy as an 80t and rejects it.
I incorporated this repository and ran the start-ide.sh script. It all came up but I cannot access /d0 and if I add a /d1 drive, it seems to not recognize it.
I'm not particularly interested in EOU or even having an IDE drive. My floppies, and my vhd hard drive images are created with toolshed utilities. I posted a query on coco pairlist and got some responses there - some related to what I wanted and some not.
I was not able to find any comprehensive documentation for xroar, but I'm under the impression that maybe the hard drive image requires a header, and am not sure I can even access the image directly.
If you can, please clarify just what is possible with xroar, and is there any way to see /d0-/d1 from the "eou_ide" intereface. Can you boot from say "-load-fd0 bootdisk.dsk -load-hd0 hdimage.vhd". If the image(s) require a header, how can this be generated?
And, I'm thinking that if a header is employed, the device descriptor has to start past this header.
Any information you can give me will be greatly appreciated. I've seen your Youtube video relating to eou_ide.
This is not an issue, but a question and since you don't have a Discussions section, I'll just go through here. I'm interested in possibly using xroar for my coco emulations instead of mame. I rarely emulate the coco, but it seems that almost every time I try in mame, they've changed the requirements, especially for floppies and get more restrictive all the time. I had this statement in my coco3 config: "ext:fdcv11:wd17xx:0 525qd" and now it seems that it won't accept this. It also seems to view a ds-40t floppy as an 80t and rejects it.
I incorporated this repository and ran the start-ide.sh script. It all came up but I cannot access /d0 and if I add a /d1 drive, it seems to not recognize it.
I'm not particularly interested in EOU or even having an IDE drive. My floppies, and my vhd hard drive images are created with toolshed utilities. I posted a query on coco pairlist and got some responses there - some related to what I wanted and some not.
I was not able to find any comprehensive documentation for xroar, but I'm under the impression that maybe the hard drive image requires a header, and am not sure I can even access the image directly.
If you can, please clarify just what is possible with xroar, and is there any way to see /d0-/d1 from the "eou_ide" intereface. Can you boot from say "-load-fd0 bootdisk.dsk -load-hd0 hdimage.vhd". If the image(s) require a header, how can this be generated?
And, I'm thinking that if a header is employed, the device descriptor has to start past this header.
Any information you can give me will be greatly appreciated. I've seen your Youtube video relating to eou_ide.