lah@raybed2.UUCP (LANCE HOLMES) (10/21/88)
I have been experimenting with the new 1.3 workbench and having a 2000
with a micron board I also have tried using the Rad: setup as shown
in the manual. I tried using the diskcopy as show:
"sys:system/diskcopy df0: to rad:"
and found that it didn't work
I noticed that the manual doesn't really talk about diskcopy in the
section which talks about the programs located in the systems draw.
(guessing at the answer):
do I need the 1.3 kickstart rom in my 2000 in order for the diskcopy to
work. Presently I use the readkwik routine which I think I will still
prefer because I can save a little more than 880k on a disk.
I realize that autoboot won't work.
Also after reading some previous posted messages if you have a hard
disk drive and have the 1.3 kickstart are you forced to choose between
autoboot of the hard drive or ffs. but not both.
Lance Holmespapa@pollux.usc.edu (Marco Papa) (10/22/88)
In article <1231@raybed2.UUCP> lah@raybed2.UUCP (LANCE HOLMES) writes: |I have been experimenting with the new 1.3 workbench and having a 2000 |with a micron board I also have tried using the Rad: setup as shown |in the manual. I tried using the diskcopy as show: | "sys:system/diskcopy df0: to rad:" |and found that it didn't work For diskcopy to work between df0: and rad: they must be of the same size, that is 880K. The supplied mountlist has to be modified with: Lowcyl = 0 ; Highcyl = 79 -- Marco Papa 'Doc' -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= uucp:...!pollux!papa BIX:papa ARPAnet:pollux!papa@oberon.usc.edu "There's Alpha, Beta, Gamma and Diga!" -- Leo Schwab [quoting Rick Unland] -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
peter@sugar.uu.net (Peter da Silva) (10/23/88)
In article <1231@raybed2.UUCP>, lah@raybed2.UUCP (LANCE HOLMES) writes: > I have been experimenting with the new 1.3 workbench and having a 2000 > with a micron board I also have tried using the Rad: setup as shown > in the manual. I tried using the diskcopy as show: > "sys:system/diskcopy df0: to rad:" > and found that it didn't work Well, you do have to increase the size of RAD: in your mountlist to 79 cylinders. (by the way, specifying a RAM disk in cylinders gives me a weird sensation, as if I was using some sort of victorian technology as my main memory) > Also after reading some previous posted messages if you have a hard > disk drive and have the 1.3 kickstart are you forced to choose between > autoboot of the hard drive or ffs. but not both. No. You just have to have a SFS autoboot device somewhere. With a hard disk you can either set up an autobooting RAD: or a SFS partition on your hard drive. One odd thing I've noticed, I can't autoboot my RAD: in my 1000. It's obvious why, though. No mystery... you need autoconfig RAM to do it. -- Peter da Silva `-_-' peter@sugar.uu.net Have you hugged U your wolf today? Disclaimer: I accept full responsibility for my own typos.
adam@cbmvax.UUCP (Adam Levin CATS) (10/24/88)
There are explicit directions on the bottom of page 5-5 and the top of page 5-6 of the Enhancer Software manual to allow a DiskCopy to RAD:. Basically, you must change RAD's HighCyl (in :devs/MountList) from 7 to 79. Note that if you do this after mounting RAD:, you must turn your Amiga off and then on (always wait 30 seconds between these two actions).
phils@tekigm2.TEK.COM (Philip E Staub) (10/25/88)
Sorry to post this, but you know the story: the mailer bounced it: In article <1231@raybed2.UUCP> lah@raybed2.UUCP (LANCE HOLMES) writes: > >I have been experimenting with the new 1.3 workbench and having a 2000 >with a micron board I also have tried using the Rad: setup as shown >in the manual. I tried using the diskcopy as show: > "sys:system/diskcopy df0: to rad:" >and found that it didn't work > Have you tried checking the MountList entry for RAD:, to ensure that it has the same number of surfaces, cylinders and sectors as a 3.5" floppy? Also, after you make any changes to the mountlist entry for RAD:, physically *remove the power* from your Amiga, so that any RAD: that currently exists will no longer be there. A simple warm reboot doesn't do it. I'm not sure, but I doubt that RemRAD does either. Using these methods, I have had no trouble getting diskcopy to work, without 1.3 kickstart. >I noticed that the manual doesn't really talk about diskcopy in the >section which talks about the programs located in the systems draw. > >(guessing at the answer): > >do I need the 1.3 kickstart rom in my 2000 in order for the diskcopy to >work. Presently I use the readkwik routine which I think I will still >prefer because I can save a little more than 880k on a disk. >I realize that autoboot won't work. > >Also after reading some previous posted messages if you have a hard >disk drive and have the 1.3 kickstart are you forced to choose between >autoboot of the hard drive or ffs. but not both. > Some experimenting I've done suggests that you *must* have at least one old filesystem partition on the hard disk. I've tried it with only ffs, and it just locks up. > >Lance Holmes Good Luck, Phil ------------------------------------------------------------------------------ Phil Staub Tektronix, Inc., Vancouver, Washington 98668 phils@tekigm2.MEN.TEK.COM -- ------------------------------------------------------------------------------ Phil Staub Tektronix, Inc., Vancouver, Washington 98668 phils@tekigm2.MEN.TEK.COM
lphillips@lpami.van-bc.UUCP (Larry Phillips) (10/26/88)
[Line eater? What's a li In <3688@tekigm2.TEK.COM>, phils@tekigm2.TEK.COM (Philip E Staub) writes: > Some experimenting I've done suggests that you *must* have at least one old > filesystem partition on the hard disk. I've tried it with only ffs, and it > just locks up. It depends on the controller. Any controller mounted with the MOUNT command can be all FFS. I have been running a Wedge that way ever since getting a beta FSS for testing with early Wedge software. -larry -- If all the MSDos machines were laid end to end, they still wouldn't be as fun as a single Amiga. +----------------------------------------------------------------+ | // Larry Phillips | | \X/ {ihnp4!alberta!ubc-vision,uunet}!van-bc!lpami!lphillips | | COMPUSERVE: 76703,4322 | +----------------------------------------------------------------+
mikes@lakesys.UUCP (Mike Shawaluk) (10/28/88)
In article <1231@raybed2.UUCP> lah@raybed2.UUCP (LANCE HOLMES) writes: > >I have been experimenting with the new 1.3 workbench and having a 2000 >with a micron board I also have tried using the Rad: setup as shown >in the manual. I tried using the diskcopy as show: > "sys:system/diskcopy df0: to rad:" >and found that it didn't work >... >do I need the 1.3 kickstart rom in my 2000 in order for the diskcopy to >work? >... >Lance Holmes I have been able to DiskCopy from a floppy to RAD:, but the last system disk I set up to do this was under 1.3 Gamma 3 or so. Actually, it was a Three Stooges boot disk (!). Anyways, you are aware (I assume) that the RAD: mount list information must specify it as an 80 track device. Anyways, I've done this on my A1000 with KickStart 1.2; I've even been able to get the ramdrive.device to work _under_ 1.2 (AmigaDOS, that is), but since I just got my 1.3 Enhancer today (hurray!), I'm going to re-try everything to make sure it still works. BTW, the DiskCopy really cranks (about 2 tracks/second)! -- - Mike Shawaluk (...!uunet!uwmcsd1!lakesys!mikes)
phils@tekigm2.TEK.COM (Philip E Staub) (10/28/88)
In article <1930@van-bc.UUCP> lphillips@lpami.van-bc.UUCP (Larry Phillips) writes: |In <3688@tekigm2.TEK.COM>, phils@tekigm2.TEK.COM (Philip E Staub) writes: |> Some experimenting I've done suggests that you *must* have at least one old |> filesystem partition on the hard disk. I've tried it with only ffs, and it |> just locks up. | | It depends on the controller. Any controller mounted with the MOUNT |command can be all FFS. I have been running a Wedge that way ever since |getting a beta FSS for testing with early Wedge software. | Nope. Must be something else. I *am* using MOUNT. Also, it can't be because of 1.2 ROMS. I tried 1.3, too, and it still locks. I guess I'll keep looking. Phil -- ------------------------------------------------------------------------------ Phil Staub Tektronix, Inc., Vancouver, Washington 98668 phils@tekigm2.MEN.TEK.COM