raw@mcnc.org (Russell Williams) (05/30/89)
I have a problem using the RAD: device with my Amiga 1000. The system used to be a 756K amiga with the kickstart eliminator running 1.2 with a 1.3 workbench. When I got 1.3, I tried to implement the RAD: device on a modest level, around 30 cylinders, just to use it as a WordPerfect file backup. It would mount successfully, but would guru when I tried to reboot the system. About now, most of you are probably saying "But you're using 1.2 kickstart! There's your problem!" Well, I thought so too. I just forgot about it and went my merry way. Then I purchased two megs of memory. Now I could really scramble with the old RAD: device, so I bought the 1.3 kickstart upgrade roms from CMI. I mounted a huge RAD:, 1.7 megs worth, and boom, it gurued again. Every time I reboot, it gurus. I can't figure out what it's doing now. Has anybody else had trouble with RAD: blowing the system? Thanks, Russell
raw@mcnc.org (Russell Williams) (05/30/89)
Well, it occured to me that I had overlooked the completely obvious. I took out the addmem statement at the beginning of the startup-sequence, and now it works fine. I don't know if I thought of that with the 1.2 roms or not. This is unusual because whenever anything goes wrong I almost always start looking at the addmem statement. Can anybody tell me if there's a way to get around this problem, as the 256k sometimes makes a crucial difference. The problem I have now is with the diskcopy statement from CLI. I can't seem to get the format down. I must be overlooking the obvious again, but I can't seem to figure it out. The format I started off with was: SYS:System/diskcopy <nil: df0: to RAD: After that, I tried this: SYS:System/diskcopy df0: to RAD: Then, I tried: Sys:System/diskcopy workbench1.3: to RAD: Then, in frustration, I tried: Sys:System/diskcopy df0: to df1: All of these attempts resulted in the same message, which was the diskcopy template. I must be messing up the format, since I keep getting a message telling me what format diskcopy is looking for. That implies the command is being loaded in, it just doesn't recognize what I want. I'd be very grateful for any help in this matter. Russell
deven@rpi.edu (Deven Corzine) (05/30/89)
In article <4571@alvin.mcnc.org> raw@mcnc.org (Russell Williams) writes: > Well, it occured to me that I had overlooked the completely > obvious. I took out the addmem statement at the beginning of the > startup-sequence, and now it works fine. I don't know if I thought > of that with the 1.2 roms or not. This is unusual because whenever > anything goes wrong I almost always start looking at the addmem > statement. Can anybody tell me if there's a way to get around this > problem, as the 256k sometimes makes a crucial difference. I haven't had occasion to use AddMem, but my first instinct is to simply move it to AFTER mounting RAD:... > The problem I have now is with the diskcopy statement from > CLI. I can't seem to get the format down. I must be overlooking > the obvious again, but I can't seem to figure it out. The format I > started off with was: [examples] > All of these attempts resulted in the same message, which was the > diskcopy template. I must be messing up the format, since I keep getting > a message telling me what format diskcopy is looking for. That implies the > command is being loaded in, it just doesn't recognize what I want. I'd be > very grateful for any help in this matter. I'm not sure what it is; your examples looked fine to me, and "diskcopy df0: to df0:" worked fine for me, off both Workbench 1.3 and the old 1.2... perhaps something else is messing up your input? (like a shell?) give it a try from a vanilla CLI and see if that works... Deven -- shadow@[128.113.10.2] <shadow@pawl.rpi.edu> Deven T. Corzine (518) 272-5847 shadow@[128.113.10.201] <shadow@acm.rpi.edu> 2346 15th St. Pi-Rho America deven@rpitsmts.bitnet <userfxb6@rpitsmts> Troy, NY 12180-2306 <<tionen>> "Simple things should be simple and complex things should be possible." - A.K.
Sullivan@cup.portal.com (sullivan - segall) (05/31/89)
> > The problem I have now is with the diskcopy statement from CLI. I >can't seem to get the format down. I must be overlooking the obvious again, >but I can't seem to figure it out. The format I started off with was: > > SYS:System/diskcopy <nil: df0: to RAD: [more futility deleted] > > All of these attempts resulted in the same message, which was the >diskcopy template. I must be messing up the format, since I keep getting >a message telling me what format diskcopy is looking for. That implies the >command is being loaded in, it just doesn't recognize what I want. I'd be >very grateful for any help in this matter. > >Russell diskcopy only works with devices which are of the same size. To use diskcopy to RAD: you have to define a RAD device which matches the size of a floppy in tracks, and sectors per track. The (only) error message returned by diskcopy is LESS THAN HELPFUL in this regard. The same reply is returned if the device isn't mounted, if it is a non=DOS diskette, it the driver couldn't be opened, if the filesystem couldn't be found, ... grrr. -Sullivan Segall _________________________________________________________________ /V\ Sullivan was the first to learn how to jump without moving. ' Is it not proper that the student should surpass the teacher? To Quote the immortal Socrates: "I drank what?" -Sullivan _________________________________________________________________ Mail to: ...sun!portal!cup.portal.com!Sullivan or Sullivan@cup.portal.com
detert@lognet2.arpa (CMS David K. Detert) (05/31/89)
I don't know if this is true or if it will help, but I seem to remember some correspondence some time ago that indicated you have to mount a RAD: type device similar to a disk device, i.e., 880K, etc. Discopy will only work from one disk drive type device to another, not to standard type RAM. I don't know if that explains it enough, but maybe someone else will remember what I am trying to refer to. Cheers, Dave CMSgt David k. Detert, USAF ARPANet: detert<at>lognet2.arpa
billsey@agora.UUCP (Bill Seymour) (06/01/89)
From article <4570@alvin.mcnc.org:, by raw@mcnc.org (Russell Williams):
:
: I have a problem using the RAD: device with my Amiga 1000. The system
: used to be a 756K amiga with the kickstart eliminator running 1.2 with a 1.3
: workbench. When I got 1.3, I tried to implement the RAD: device on a modest
: level, around 30 cylinders, just to use it as a WordPerfect file backup. It
: would mount successfully, but would guru when I tried to reboot the system.
: About now, most of you are probably saying "But you're using 1.2 kickstart!
: There's your problem!" Well, I thought so too. I just forgot about it and
: went my merry way.
: Then I purchased two megs of memory. Now I could really scramble with
: the old RAD: device, so I bought the 1.3 kickstart upgrade roms from CMI. I
: mounted a huge RAD:, 1.7 megs worth, and boom, it gurued again. Every time
: I reboot, it gurus. I can't figure out what it's doing now. Has anybody
: else had trouble with RAD: blowing the system?
Sounds like you may be doing the 'Addmem' before mounting RAD:. Note
that the first access to RAD: has to happen before doing the Addmem also.
Once you accessed RAD: even once, the memory is allocated and you can go
ahead and add the KS memory with no worries.
: Thanks,
:
: Russell
--
-Bill Seymour ...tektronix!reed!percival!agora!billsey
...tektronix!sequent.UUCP!blowpig!billsey
Creative Microsystems Northwest Amiga Group At Home Sometimes
(503) 691-2552 (503) 656-7393 BBS (503) 640-0842