Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: MickTheLip on March 25, 2007, 10:53:08 PM
-
I've just revived the GVP HDD and I have it on a A500 with the 1.3 rom.How do I install the workbench to it?At the moment I have it booting off the HDD and it boots to an Amiga DOS window Release 1.3 with the following line. 1>curser
What do I need to do now? I have formatted the HDD into 2 partitions one named Workbench the other as DH0.
-
MickTheLip wrote:
I've just revived the HDD and I have it on a A500 with the 1.3 rom.How do I install the workbench to it?At the moment I have it booting off the HDD and it boots to an Amiga DOS window Release 1.3 with the following line. 1>curser
What do I need to do now?
It's been awhile since I installed 1.3, but I think you need to :
1) Boot off the 1.3 workbench disk
2) Copy the entire contents of the workbench disk to the HDD
3) Edit the startup-sequence and rename and references to DF0: to DH0: (or whatever your HDD is called)
-
I've tried booting off the HDD then inserting the Workbench 1.3 disc and then typing the following.
DF0:c/copy DF0:to DH0:ALL QUIET
I then get this message come up on screen.
Can't open DF0:to for input-Error Code 205
Any pointers to what this means?
-
It's a syntax problem. Thanks for putting in the exact text you entered, it helps greatly in seeing what happened.
It appears that you did not leave a space between DF0: and the word "to". So it's trying to open "DF0:to".
It's been a LONG time since I looked up the syntax for AmigaDOS copy but I think that your use of keyword ALL is the right idea, but again you need a space there.
I am sure that there were better ways, scripts to handle HD installation, but am not certain that they were included at the point that WB 1.3 was standard. I know my 1.3 machine was floppy based. WB 2 had a hard disk script I am pretty sure.
I think that the word "to" was optional. But if you just paste it back in and make it read:
DF0:c/copy DF0: to DH0: ALL QUIET
then it should work. PaulT1
-
I've manually dragged all the drawers off the Workbench 1.3 onto the DH0:partition.How do I access the startup sequence to change any DF0: lines to HD0:????
-
Any text editor will do.
There should be a copy of notepad that came standard with your workbench that you can load your startup-sequence up and edit it.
-
I'll have to stop working on it tonight! Every time I enter that line and return it the HDD noise level increases so much it sounds like its trying to take off.I'll try retyping the line in with that space and see if that sorts it out as far as the syntax error goes later in the day.If I can get it sorted out on this huge 50mb HDD then when I get hold of a bigger drive I'll be adept enough to sort it.
What really gets me is the noise the drive makes is this par for the course so to speak?
-
I hope when you dragged the drawers you set it to show all files and dragged the ones without icons too. It might be safer to do ths from the command line:
1.> DF0:C/Copy DF0:#? DH0: ALL CLONE
should recursively copy everything. Then use notepad to edit the startup-sequence on DH0: and change any reference to DF0: to DH0:.
--
moto
-
There isn't any "show all files" option in WB 1.3?
I was in the exact same situation some days ago. I copied all the files and directories in cli, but as far as I remember, I didn't need to change any references to DH0: to make it work.
-
madsjm wrote:
There isn't any "show all files" option in WB 1.3?
Oh ok, I haven't used 1.3 for about 10 years :-) In that case you definitely need to use the CLI to copy the files. I have just tested the syntax I posted above and it works.
madsjm wrote:
I was in the exact same situation some days ago. I copied all the files and directories in cli, but as far as I remember, I didn't need to change any references to DH0: to make it work.
They must use SYS: in the startup-sequence. Mick - just copy the files as above then try it without modifying the s-s, and if you have any problems like "No disk present in device DF0:" then check the s-s it for references to DF0:.
-
There is no SHOW ALL FILES in WB1.3. That came with 2.04 or 1.4A for A3000.
If you copy all content from floppy to DH0:, you don't have to worry about modifying SS - there are startup-sequence.hd and startupII scripts used to boot off HDD.
WB1.3 is quite a challenge if you try to build a system around it. For instance, try getting a SCSI CDROM up&running...hard deal, but it works!
-
I think I'm going to install a 1.3 environment just for old times sake, and to see if I can cope without the much more friendly 3.9 :-)
--
moto
-
@Mick
You really need some documentation! Amiga OS is famous for its eligant design and features. This includes the textural Command Line Interface (CLI or Shell) as well. The syntax is easy and well thought-out, one of the best on any platform. You can issue any command with a ? after it (that's COMMAND space question-mark, grin) to get a listing of valid parameters, but, you need some info to interpret the listing. OS 1.3 relied more heavily on the CLI to suppliment the features of Workbench.
You should find some books on e-bay.
"The Amiga Dos Manual" any edition, the commands are the same
"The Amiga Companion" Rob Peck, excellent tutorials and useful examples
"AmigaDos" Commodore, very good, many copies published
"Introduction to the Amiga 500" Commodore, general operations
Any of these would be an excellent reference for the CLI, writing script files, etc. I don't know how you'll get along without one.
"Best Amiga Tips and Tricks" Denny Adkins, not about CLI but excellent anyway
@ anyone
Are any of these books reproduced on-line? I didn't see these kinds of specifics on Amiga-wiki.
-
An alternative to the CLI is to use a Dir Utility like Directory Opus (on Aminet). Again, the Amiga platform is blessed with the best dirutils on any platform, this is no exaggeration! Dopus was cloned to Linux as Worker for this reason. Windows Explorer is a very pale excuse compared to the top 10 such programs on the Amiga. Some choices available on Aminet for free include:
Directory Opus, ver 4.1x, very good and most popular
Ordering, rediculously fast even at 7Mhz, requirs few resources
Disk Master
ClickDos
All are pre-configured but can be customized with the commands you use most. This is were those manuals come in handy again. Many people have uploaded their Dopus configureations for others to study, improve, etc.
-
I've had various options of what to type in.The following has finally seemed to have cracked it.
1> DF0:C/Copy DF0: to DH0: ALL QUIET
The difference seems to have been C not c and spacing.
Something has at long last been (by HDD light activity) been copied across to the HDD.I'll now reboot it to see what happens!!!!
-
Job accomplished it now boots through Worbench and shows 4967872 free memory.So it appears I have the RAM in the HDD being accessed as well as the i/2meg trapdoor RAM.It would also appear the Workbench is version 34.28 Kickstart Version 34.5 and also has Virus X 4.01 by Steve Tibbett installed and running on it.Dread to think how out of date that must be now.I've rebooted several times now and it is rebooting everytime with no problems.What really gets me is the noise the drive makes.Sounds like a hovermower.Thanks every body for all your input and list of reading material that will obviously be of immense help!!!
-
Spoke too soon Icons do not open when clicked on and pointer freezes.Damn! Damn! DAMN!Second time I rebooted and clicked on DH0 icon and it opens but cannot open any of the drawers.Rebooted refuses to open DH0: again and pointer freezez. Something is definitely wrong here but each reboot ends either at trying to open DH0: or trying to open one of the drawers???????
-
Diging about in my Software I managed to find another 1.3 Workbench disc and so I formated the HDD and reinstalled the Workbenmch 1.3 Unforunately still the same sorts of problems.Begining to think it's hardware problems.The A500 disc drive appears to be a bit sporadic and I'm thinking the Keyboard is on the blink as well. Some keys appear to lack function as well!The HDD needs a bigger HDD anyway so it looks like s complete stripdown to check everything is in place in the A500 or not.I also wonder if the trapdoor memory upgrade is also causing problems by clashing with the HDD onboard memory?
-
You have been reporting a loud hard drive and strange floppy behavior all along. Unless you are running a strange trap-door memory card, like the one from ICD, there should be no memory conflict with fast memory.
Replacing the hard drive would solve one problem. Mating the GVP to the A500+ might solve the other if its floppy is more reliable. Yes, you can still load Workbench 1.3 to the HDD while running 2.x roms (for compatibility with both roms).
As you may notice from other threads here, replacement floppy drives are in short supply. Maybe a cleaner disk will help.
This would be a no-brainer for me. The A500+ with greater memory and newer rom would make better use of the GVP
-
The maximum fast ram on an A500 is 8 mb. If I were you, I would max out the HD+ memory and get rid off the expansion slot memory. Then you may consider upgrading chip mem.
The FFS which comes with kick 1.3 is not very friendly with large HDDs / partitions. I remember having a really hard time getting a 1gb drive to work with both an A590 and Gvp HD+ and finally giving up. It worked a treat with kick 3.1. Just my two yens.
-
Been exploring this A500 I got in a lot with the GVP HDD.After discovering the state of the HDD. I suppose it should not come as too much of a surprise to have found the A500 is a real heap of problems to!!! In fact the whole writeup for the sale was very economical with the truth.As far as testing went what on earth did they test? The only thing that I've found in the lot without a problem is a Robo Shift interface for Mouse and joystick auto swap.
-
I've got another GVP HDD of 105mb coming the next day or so.It has 4mb of memory on board and 2 4mb chips spare. So one way or another it gives me more options to find out what is faulty and what needs replacing!!!In the meantime I'm about to commit surgery on the A500 powerpack(faulty cable with frayed wires!!!)and the A500.Will try out the HDD on the A500+ to see what happens in the meantime.Got my A2000 delivered yesterday so now got another toy to play with!!!