[Coco] Floppy - less boot , was Re: VI and VIRQ
mark at cloud9tech.com
Tue May 13 20:03:19 EDT 2008
Quick look here.
Looks like you have the 80T /d0 descriptor selected. Select d0_35s.
Then you need to make sure your script is formatting as SS.
Then make sure that you merge the correct loader for SS floppy. I have
done it, been awhile but it does work.
Hopefully that helps.....
Quoting Diego Barizo <diegoba at adinet.com.uy>:
> Now that it comes to mention. I've been trying to create a custom 1s35t
> boot disk for my HDB-DOS / SuperIDE setup, completely unsuccessfully so
> Looking around, I found a mention of the bug in the rb1773 driver, and
> the symptoms match the ones I see, freezing after tb ...... at boot
> Will this bug affect an attempt to boot from a HDB-DOS virtual drive?
> When I try that, I get all the ..... at boot, and then bCCCC%%V Date
> Save Unlink GrfDrv Backup Date # t*j , and final freeze.
> Here is my bootlist file, which could be the cause of my problems...
> * Kernel/System Section
> * These modules are mandatory.
> * RBF Section
> * DriveWire driver (Cloud-9 product)
> * DriveWire descriptors - select as needed
> * SuperDriver Package (Cloud-9 product)
> * Select Low level SCSI and/or IDE driver
> * SuperDriver descriptors - select as needed
> * SCSI descriptors (IDs 0-7)
> * SCSI HDB-DOS descriptor
> * IDE descriptors (master/slave)
> * IDE HDB-DOS descriptor
> * WD1773 floppy support for Tandy and compatible disk controllers
> * WD1773 floppy support for Disto Super Controller II
> * Floppy device descriptors
> * DD - default device - choose one if needed
> * D0 - drive 0 - choose one if needed
> * D1 - drive 1 - choose one if needed
> * D2 - drive 2 - choose one if needed
> * D3 - drive 3 - choose if needed
> * RAMDisk driver
> * RAMDisk descriptors - select as needed
> * Memory device descriptor
> * SCF Section
> * CoCo 3 I/O driver
> * Joystick modules: choose Joystick OR
> * (M)icrosoft or (L)ogitech mouse using 6551 or 6552 ACIA
> * CoGrf/CoWin subroutine module
> * Use CoWin with Multi-Vue; use CoGrf
> * for basic text and graphic window support..
> * Select only one.
> * CoVDG I/O subroutine module
> * Select one or both
> * Select only one term descriptor
> * Select as many window descriptors as needed
> * Select as many VDG window descriptors as needed
> * Serial port drivers
> * CoCo Bit-Banger terminal port
> * 6551 ACIA
> * Tandy Modem Pak
> * Printer drivers
> * VRN is a driver module used by certain games, including King's Quest III,
> * Leisure Suit Larry and Flight Simulator II. A /nil descriptor is also
> * supported.
> * Pipe Section
> * Pipes are a useful but optional part of a system.
> * Clock Section
> * Select one clock module depending upon your power line frequency
> * (60Hz = USA/Canada; 50Hz = Europe, Australia)
> * Select one clock2 module that supports your real-time clock, if any.
> * Besides support for the internal software clock, the following
> * hardware clocks are supported: Burke & Burke, Disto 2-N-1, Disto 4-N-1,
> * Eliminator, Harris, SmartWatch, Cloud-9, the MESS emulator, Jeff
> * Vavasour's CoCo emulator, and DriveWire.
> * System Kick-Start Module
> * Choose which startup module you wish to use. (sysgo_dd is recommended
> * for most configurations.)
> * Alternatively, this module can reside in the root directory of the
> * boot device, saving precious system RAM.
>> Any idea about the rest of it, like the non booting ss35 disk? Or
>> is it possible to do a basic "backup 0 to 127" from a 40 track DS
>> disk? (my setup is a 1GB scsi disk, with HDB-DOS new enough to
>> handle virtual floppies, but I don't recall what size the virtual's
>> are, os9 side formatted for 4 sector clusters)
>> Which brings up the question, is it possible to access these
>> virtual disks from nitros9 with a carefully crafted SO, S1 etc
>> descriptors for rbsuper?
>>> Boisy G. Pitre
>>> Email: boisy at boisypitre.com
>>> Web: http://www.boisypitre.com
>>> Coco mailing list
>>> Coco at maltedmedia.com
> Coco mailing list
> Coco at maltedmedia.com
More information about the Coco