11/25/07: Disk Image Help Needed by HJR, | Category: OS-9 | 13 comments - (Comments are closed)

Disk Image Help Needed

Now that I have my NitrOS-09 downloads I’m having a problem. I have an old 386 that has both the 3.5 and 5.25 floppy drives so I downloaded to my main PC, moved the files to the 3.5 and put them in the 386. I formated a 5.25 floppy with the CoCo and ran the DSKINI program from DOS in the 386 and it tells me that it was successful in retrieving the image. Problem is when I try to check the disk in the CoCo with DIR0 it checks the disk for a couple of seconds and gives me an IO error. Am I doing something wrong here?
TIA!

-HJR

13 comments to Disk Image Help Needed

  • tlindner

    The disks from the NitrOS-9 project do not contain RSDOS directories.

  • RobertGault

    Many things may be wrong and probably several are. The first and biggest problem was your attempt to read an OS-9 directory with Disk Basic. That must be what you did since you used the command “DIR0″ (Disk Basic) instead of “dir /d0″ (OS-9 command).

    Does this mean the disk is bad? Not necessarily. A good OS-9 disk frequently gives I/O errors with DIR.
    Is the disk good? Not necessarily. The program dskini.exe was not written to work with OS-9 disk images. It will work only if the disk image is single sided.

    There are several other programs that can be used with a PC to create a Coco floppy. Crucial is the OS on the PC. Tell us what OS you are using and we can suggest options.

    You should also specify which NitrOS-9 image you are using to make a real floppy. The distribution in addition to having both 6809 and 6309 code, has various single/double sided and 40/80 track images. Some of these images will only be usable with a 3.5″ drive on a Coco. Others require the Coco to have a double sided drive.

  • HJR

    Ah, okay. Assuming the disk is good how do I access it? Is there a way to boot a CoCo from a floppy?

    I’m using the 6809 40 track version for the 5.25 floppies. The one that’s available [url=http://sourceforge.net/projects/nitros9]here.[/url]

    The 386 I’m using had MS-DOS 6.22 with Windows 3.11. I’m running the DSKINI from DOS. My CoCo has a FD-502 floppy controller and drive.

    Thanks for the help!

  • RobertGault

    Right, if you used the 6809, 40 track, single sided, NitrOS-9 image to make the Coco floppy with DSKINI, then the disk will be bootable into NitrOS-9.

    I think but am not sure that the FD-502 has DOS1.1 and if so, place the disk in drive-0 and enter DOS. The disk should boot into NitrOS-9. If your controller has DOS1.0, then I’ll need to send you the *.BAS program that does what the DOS1.1 DOS command would do.

    Let’s say you have success and the disk does boot. You will see the boot message and will be asked to enter the date and time. At that point you can look at the directory with the command: dir

  • HJR

    Well, the floppy drive is responding to the DOS command in Disk Basic, but I’m still getting the IO error. I’m trying to figure out what I’m doing wrong, I do have a couple of variables I’ll throw out, but I don’t know that they’ll make a difference.

    1) I’m using 1.2 meg double side/double density floppies. I know that’s too much for the CoCo drive, but they do format as 360K and I can store and retrieve files from them with no problems.

    2) The 386 has a 1.2 meg floppy drive. But obviously it is backwards compatible, and since the DISKINI.EXE tells the drive specifically what tracks to write to is this even an issue?

    Am I on the right track here or is there something else I need to look at? :?:

  • HJR

    YES! I got it working! [img:cf7d35c113]http://i38.photobucket.com/albums/e104/ToughOldFord/Smilies/icon_clap.gif[/img:cf7d35c113] It was the floppies, I dug around and found some 360K floppies (and the write-protect stickers.) and tried it again and now I can boot to NitrOS-9. 8)

    Now a stupid question, what’s the second disk for?

    BTW, I found you can’t write protect the boot disk. :roll:

  • RobertGault

    You can try using HD disks if you tape the HD hole. Some people can get that to work and report stable disks. Others report that the data is rapidly lost as the magnetic head strength is too low to make good recordings on an HD disk in MD mode.

    Note that NitrOS-9 will not fit on a single 40 track double sided disk, but will on an 80 track double sided disk. The distribution has a 40 track disk#1 and disk#2 which combined contain what is on the 80 track disk.
    Disk#2 contains a NITROS9 directory within which are all the modules and scripts used to create custom boot disks. You won’t need disk#2 until you get further into OS-9.

    You should also note that the NitrOS-9 distribution is intended for use on a real Coco with floppy drives. Some modification will be needed to get a system that works with a hard drive. Additional modification probably will be needed to get all the bells and whistles working on emulators.

  • HJR

    Thanks for the help and info Robert, hopefully I’ll get the hang of this soon. Right now I’m just browsing through the help area in NitrOS checking out all the commands and what they do.
    For the time being my CoCo will just be running on floppies, don’t have any plans for a hard drive for it unless one falls in my lap or the need arises. However I would like to add a second floppy drive to that second bay, so I’ll keep my eyes open for one.

    8)

  • HJR

    Arrg, don’t mean to be a pest, but I’m having problems still. I’ve downloaded some games and demos .(dsk) from a couple of links in these forums. I’ve used the DSKINI.EXE to make my CoCo disks, the same way I’ve made my NitrOS-09 disks, and although dskini reports success when I run a directory check I get nothing, it just tells me okay. It acts like it’s a blank floppy. Tried it a few times with different images and the end result is always the same. The bottom line is that the NitrOS disks are the only ones I’m successful with. And I’m using the proper 360K disks this time.
    What am I doing wrong here? :?:

  • RobertGault

    You are not a pest! If anyone thought that, this forum would not be here.

    Well, I’ll go through the mantra that should be posted on very Help site. Post in detail all specifics related to the task that is causing a problem. Leave nothing out! Include any error messages, the hardware and OS in use, and any descriptions of the system status after the problem occurs that seem relevant. We don’t read minds and can’t provide help without information.

    List one or more specific disk images (url) so we can test them. Post the command sequence used with DSKINI.EXE. Report how you did the directory check, Disk Basic DIR or OS-9 dir /d0. If OS-9, indicate the descriptor values for the drive used (/d0) which can be found with ‘dmode /d0′.

  • HJR

    Thanks for the patience Robert, here’s what I’ve got:

    The afore mentioned 386 with MS-DOS 6.22 for running the DSKINI.EXE
    I have a CoCo 3, stock 128K, 6809. FD-502 floppy drive and controller.

    First I tried the files mrnukem posted at [url=http://www.coco3.com/modules.php?name=Forums&file=viewtopic&t=442]this[/url] thread.

    Then I downloaded the collection at [url=http://www.cocoquest.com/]this[/url] site.

    I’ll use the first file of that second link as my example.

    I insert a freshly formatted, by the CoCo, floppy in the 386.
    I go to the directory where I have the files stored and type:

    DSKINI/T40/D B: NICKPAK1

    And the program goes though it’s process of formating/writing and tells me when it’s done.

    First I try Disk Basic and do a DIR0 and it reads the drive and says “OK”. That’s all it does.

    If I try a DIR out of NitrOS it reads the drive and comes up with a #247 error.

    So far that’s what’s happened on every .DSK file I’ve tried except the NitrOS files, those work fine for me. (Heh, now that I’m using the proper floppies anyway.)

    You’ve lost me on the descriptor values, I don’t know what that is.
    Any idea what I’m doing wrong?

  • RobertGault

    The command
    DSKINI/T40/D B: NICKPAK1
    indicates that a 40 track double-sided disk should be written in drive B. By itself there is nothing wrong unless the image does not match that specification.

    The first question would be does the name in the command match the name of the disk image. I’d say maybe not, as most images end in .dsk or .os9 .
    The second question would be are the images 40 track double sided. While I’m not completely sure about what you used on site#2, site#1 has a zip file containing .dsk images of either 157K or 180K. That means single sided 35 or 40 track images. Oh by the way they are all Disk Basic not OS-9 images.

    The command should be:
    DSKINI B: NICKPAK1
    or
    DSKINI B: /T40 NICKPAK1

    So what happened? A double sided image alternates tracks from the front and back side of a disk. Since you told DSKINI the image was double sided, the program alternately wrote to the front and back sides of the disk when it should have put everything on the front side.

    How do you know whether an image is single or double sided without being told? 40tracksX18sectorsX256bytes=184320 and two sides = 368640

  • HJR

    You nailed it! I got ‘em working now! Thanks again for the help Robert, it’s much appreciated! [img:50ff93fbaf]http://i38.photobucket.com/albums/e104/ToughOldFord/Smilies/thumbsupwink.gif[/img:50ff93fbaf]