SHARE |
|
by Bill Degnan - 04/09/2010 09:45 | |
The problem was not the drive or the controller it was the CDOS gen. It was set to boot from a 5 1/4" drive as A, but the B drive was expected to be an 8" disk.
I needed to use CDOSGEN to generate a CDOS that expects the B drive to also be 5 1/4" Thank you to the Cromemco Google User Group (Markus and Mike) for the tip about CDOSGEN: http://groups.google.com...hread/9f180f5f17b7a009# ------------------------- First I made a backup of my only 5 1/4" disk: After booting to RDOS and at the ; prompt: (assume Return at the end of every line) A;;; S0 (that's s0 "zero" not sO) RD100 S7E00 1 [INSERT BLANK FORMATTED DISK "BACKUP DISK"] S0 WD100 S7E00 1 [INSERT ORIG DISK] SE RD100 S7E00 1 [INSERT BACKUP DISK] SE WD100 S7E00 1 [INSERT ORIG DISK] S1C RD100 S6C00 1 [INSERT BACKUP DISK] S1C WD100 S6C00 1 S0 B (to boot CDOS to new disk) then I ran CDOSGEN. --------------------- CDOSGEN (from MARCUS of the Crom group:) Here is a sample session with CDOS 2.54 CDOSGEN version 02.54 Cromemco Disk Operating System Generator Copyright (c) 1978, 1982 Cromemco Inc. Memory size (3FFF through FFFF or 16K through 64K) Drive A type (S = Small, L = Large) ? s Seek speed (1 = 6ms, 2 = 12ms, 3 = 20ms, 4 = 30ms) <1> ? 1 Single or Double sided Single or Dual density Drive B type (S = Small, L = Large, H = Hard, N = None, E = End) ? s Seek speed (1 = 6ms, 2 = 12ms, 3 = 20ms, 4 = 30ms) <1> ? 1 Single or Double sided Single or Dual density Drive C type (S = Small, L = Large, H = Hard, N = None, E = End) ? e Function key decoding (S = Standard, N = None, U = User, F = File) CDOS addresses: Starting address of CDOS (top of User Area) C700 Starting address of I/O device drivers F944 Last address used by CDOS FF41 Top of memory for this CDOS FFFF Size of CDOS 38AC Size of boot loader (maximum = 1A00) 190B Enter command file name -------------- To test type CDOS [return] with the new disk in the drive. Reply |