[Coco] Floppy - less boot , was Re: VI and VIRQ

Mark Marlette mark at cloud9tech.com
Wed May 14 08:21:00 EDT 2008


Diego,

I don't think using an 80t will work unless the boot track module is
also for that drive. The step sizes are different, 80 is 1/2 40's.

I don't think there is an 80 track boot track. I would think that it
could be made pretty easy. Hardware guys will always say that. :)

Regards,

Mark

Quoting Diego Barizo <diegoba at adinet.com.uy>:


> I was using d0_80 because my real drive 0 is an 80t, I guess that

> explains the different behavior when booting from a virtual floppy and

> from a real disk.

> The script is formatting a SS, but I was merging like this:

> merge ../MODULES/BOOTTRACK/rel_80 ../MODULES/BOOTTRACK/boot_ide

> ../MODULES/BOOTTRACK/krn>-bttemp

> Is this one the correct one?

> merge ../MODULES/BOOTTRACK/rel_80 ../MODULES/BOOTTRACK/boot_1773_6ms

> ../MODULES/BOOTTRACK/krn>-bttemp

>

> Damn, it's past midnight... to late to try it now, gonna have to wait

> 'till tomorrow :-(

>

> Diego

>

>

> Mark Marlette wrote:

>> Diego,

>>

>> 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.....

>>

>> Mark

>> Cloud-9

>>

>> 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

>>> far.

>>> 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

>>> time.

>>> 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.

>>> ../MODULES/KERNEL/krnp2

>>> *../MODULES/KERNEL/krnp3_perr

>>> *../MODULES/KERNEL/krnp4_regdump

>>> ../MODULES/SYSMODS/ioman

>>> ../MODULES/SYSMODS/init

>>> *

>>> *

>>> * RBF Section

>>> *

>>> ../MODULES/RBF/rbf.mn

>>> *

>>> * DriveWire driver (Cloud-9 product)

>>> *../MODULES/RBF/drivewire.dr

>>> * DriveWire descriptors - select as needed

>>> *../MODULES/RBF/ddx0.dd

>>> *../MODULES/RBF/x0.dd

>>> *../MODULES/RBF/x1.dd

>>> *../MODULES/RBF/x2.dd

>>> *../MODULES/RBF/x3.dd

>>> *

>>> * SuperDriver Package (Cloud-9 product)

>>> ../MODULES/RBF/rbsuper.dr

>>> * Select Low level SCSI and/or IDE driver

>>> *../MODULES/RBF/lltc3.dr

>>> ../MODULES/RBF/llide.dr

>>> * SuperDriver descriptors - select as needed

>>> * SCSI descriptors (IDs 0-7)

>>> *../MODULES/RBF/s0_tc3.dd

>>> *../MODULES/RBF/s1_tc3.dd

>>> *../MODULES/RBF/s2_tc3.dd

>>> *../MODULES/RBF/s3_tc3.dd

>>> *../MODULES/RBF/s4_tc3.dd

>>> *../MODULES/RBF/s5_tc3.dd

>>> *../MODULES/RBF/s6_tc3.dd

>>> * SCSI HDB-DOS descriptor

>>> *../MODULES/RBF/sh_ide.dd

>>> * IDE descriptors (master/slave)

>>> ../MODULES/RBF/i0_ide.dd

>>> *../MODULES/RBF/i1_ide.dd

>>> * IDE HDB-DOS descriptor

>>> *../MODULES/RBF/ih_ide.dd

>>> *

>>> * WD1773 floppy support for Tandy and compatible disk controllers

>>> ../MODULES/RBF/rb1773.dr

>>> * WD1773 floppy support for Disto Super Controller II

>>> *../MODULES/RBF/rb1773_scii_ff74.dr

>>> *../MODULES/RBF/rb1773_scii_ff58.dr

>>> * Floppy device descriptors

>>> * DD - default device - choose one if needed

>>> *../MODULES/RBF/ddd0_35s.dd

>>> *../MODULES/RBF/ddd0_40d.dd

>>> ../MODULES/RBF/ddd0_80d.dd

>>> * D0 - drive 0 - choose one if needed

>>> *../MODULES/RBF/d0_35s.dd

>>> *../MODULES/RBF/d0_40d.dd

>>> ../MODULES/RBF/d0_80d.dd

>>> * D1 - drive 1 - choose one if needed

>>> ../MODULES/RBF/d1_35s.dd

>>> *../MODULES/RBF/d1_40d.dd

>>> *../MODULES/RBF/d1_80d.dd

>>> * D2 - drive 2 - choose one if needed

>>> *../MODULES/RBF/d2_35s.dd

>>> *../MODULES/RBF/d2_40d.dd

>>> *../MODULES/RBF/d2_80d.dd

>>> * D3 - drive 3 - choose if needed

>>> *../MODULES/RBF/d3_35s.dd

>>> *

>>> * RAMDisk driver

>>> *../MODULES/RBF/rammer.dr

>>> * RAMDisk descriptors - select as needed

>>> *../MODULES/RBF/ddr0_8k.dd

>>> *../MODULES/RBF/ddr0_96k.dd

>>> *../MODULES/RBF/ddr0_128k.dd

>>> *../MODULES/RBF/ddr0_192k.dd

>>> *../MODULES/RBF/r0_8k.dd

>>> *../MODULES/RBF/r0_96k.dd

>>> *../MODULES/RBF/r0_128k.dd

>>> *../MODULES/RBF/r0_192k.dd

>>> * Memory device descriptor

>>> *../MODULES/RBF/md.dd

>>> ***************************************

>>> * SCF Section

>>> *

>>> ../MODULES/SCF/scf.mn

>>> *

>>> * CoCo 3 I/O driver

>>> * Joystick modules: choose Joystick OR

>>> * (M)icrosoft or (L)ogitech mouse using 6551 or 6552 ACIA

>>> ../MODULES/SCF/vtio.dr

>>> ../MODULES/SCF/keydrv_cc3.sb

>>> ../MODULES/SCF/snddrv_cc3.sb

>>> ../MODULES/SCF/joydrv_joy.sb

>>> *../MODULES/SCF/joydrv_6551M.sb

>>> *../MODULES/SCF/joydrv_6552M.sb

>>> *../MODULES/SCF/joydrv_6551L.sb

>>> *../MODULES/SCF/joydrv_6552L.sb

>>> *

>>> * CoGrf/CoWin subroutine module

>>> * Use CoWin with Multi-Vue; use CoGrf

>>> * for basic text and graphic window support..

>>> * Select only one.

>>> *../MODULES/SCF/cogrf.io

>>> ../MODULES/SCF/cowin.io

>>> *

>>> * CoVDG I/O subroutine module

>>> * Select one or both

>>> ../MODULES/SCF/covdg.io

>>> *../MODULES/SCF/covdg_small.io

>>> *

>>> * Select only one term descriptor

>>> *../MODULES/SCF/term_vdg.dt

>>> *../MODULES/SCF/term_win40.dt

>>> ../MODULES/SCF/term_win80.dt

>>> *../MODULES/SCF/term_bbt.dt

>>> *../MODULES/SCF/term_sc6551.dt

>>> *

>>> * Select as many window descriptors as needed

>>> ../MODULES/SCF/w.dw

>>> ../MODULES/SCF/w1.dw

>>> ../MODULES/SCF/w2.dw

>>> ../MODULES/SCF/w3.dw

>>> ../MODULES/SCF/w4.dw

>>> ../MODULES/SCF/w5.dw

>>> ../MODULES/SCF/w6.dw

>>> ../MODULES/SCF/w7.dw

>>> *

>>> * Select as many VDG window descriptors as needed

>>> ../MODULES/SCF/v1.dw

>>> *../MODULES/SCF/v2.dw

>>> *../MODULES/SCF/v3.dw

>>> *../MODULES/SCF/v4.dw

>>> *../MODULES/SCF/v5.dw

>>> *../MODULES/SCF/v6.dw

>>> *../MODULES/SCF/v7.dw

>>> *

>>> * Serial port drivers

>>> * CoCo Bit-Banger terminal port

>>> ../MODULES/SCF/scbbt.dr

>>> ../MODULES/SCF/t1.dd

>>> * 6551 ACIA

>>> *../MODULES/SCF/sc6551.dr

>>> *../MODULES/SCF/t2_sc6551.dd

>>> *../MODULES/SCF/t3_sc6551.dd

>>> * Tandy Modem Pak

>>> ../MODULES/SCF/modpak.dr

>>> ../MODULES/SCF/m1.dd

>>> *../MODULES/SCF/m2.dd

>>> *

>>> * Printer drivers

>>> ../MODULES/SCF/scbbp.dr

>>> ../MODULES/SCF/p.dd

>>> *

>>> * 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.

>>> ../MODULES/SCF/vrn.dr

>>> ../MODULES/SCF/vi.dd

>>> ../MODULES/SCF/ftdd.dd

>>> *

>>> ***************************************

>>> * Pipe Section

>>> *

>>> * Pipes are a useful but optional part of a system.

>>> ../MODULES/PIPE/pipeman.mn

>>> ../MODULES/PIPE/piper.dr

>>> ../MODULES/PIPE/pipe.dd

>>> *

>>> ***************************************

>>> * Clock Section

>>> *

>>> * Select one clock module depending upon your power line frequency

>>> * (60Hz = USA/Canada; 50Hz = Europe, Australia)

>>> ../MODULES/CLOCKS/clock_60hz

>>> *../MODULES/CLOCKS/clock_50hz

>>> * 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.

>>> *../MODULES/CLOCKS/clock2_soft

>>> *../MODULES/CLOCKS/clock2_bnb

>>> *../MODULES/CLOCKS/clock2_disto2

>>> *../MODULES/CLOCKS/clock2_disto4

>>> *../MODULES/CLOCKS/clock2_elim

>>> *../MODULES/CLOCKS/clock2_harris

>>> *../MODULES/CLOCKS/clock2_smart

>>> *../MODULES/CLOCKS/clock2_jvemu

>>> *../MODULES/CLOCKS/clock2_messemu

>>> ../MODULES/CLOCKS/clock2_cloud9

>>> *../MODULES/CLOCKS/clock2_dw

>>> *

>>> ***************************************

>>> * 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.

>>> *../MODULES/SYSMODS/sysgo_dd

>>> ../MODULES/SYSMODS/sysgo_h0

>>>

>>>>

>>>> 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?

>>>>

>>>>

>>>>> Regards,

>>>>> Boisy G. Pitre

>>>>> --

>>>>> Email: boisy at boisypitre.com

>>>>> Web: http://www.boisypitre.com

>>>>>

>>>>>

>>>>> --

>>>>> Coco mailing list

>>>>> Coco at maltedmedia.com

>>>>> http://five.pairlist.net/mailman/listinfo/coco

>>>>>

>>>>

>>>>

>>>>

>>>>

>>>

>>> --

>>> Coco mailing list

>>> Coco at maltedmedia.com

>>> http://five.pairlist.net/mailman/listinfo/coco

>>

>>

>>

>>

>> --

>> Coco mailing list

>> Coco at maltedmedia.com

>> http://five.pairlist.net/mailman/listinfo/coco

>>

>

> --

> Coco mailing list

> Coco at maltedmedia.com

> http://five.pairlist.net/mailman/listinfo/coco







More information about the Coco mailing list