Welcome, Guest. Please login or register.

Author Topic: help me restore my newly acquired Amiga 3000  (Read 12118 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline KremlarTopic starter

  • Sr. Member
  • ****
  • Join Date: Jul 2009
  • Posts: 393
    • Show only replies by Kremlar
Re: help me restore my newly acquired Amiga 3000
« Reply #14 from previous page: January 04, 2012, 05:23:21 PM »
Another quick question, for anyone familiar with this old Super Kickstart from disk crap.
 
I'd like to configure this hard drive as it was originally.
 
 - I know I need a WB_2.x: partition.  Can this be the only partition, or would I simply make this a small partition and have a standard DH0: partition along with it?
 
 - Do I need a WB_1.3: partition if don't want to boot to 1.3?
 
 - I know the Super Kickstart files need to be in WB_2.x:devs/kickstart.  I assume "kickstart" needs to be a drawer containing the file?  If so, does the filename matter?  Or is the file actually called "kickstart" and located in WB_s.x:devs?
 

Offline Zac67

  • Hero Member
  • *****
  • Join Date: Nov 2004
  • Posts: 2890
    • Show only replies by Zac67
Re: help me restore my newly acquired Amiga 3000
« Reply #15 on: January 04, 2012, 08:18:52 PM »
Quote
- I know I need a WB_2.x: partition.  Can this be the only partition, or would I simply make this a small partition and have a standard DH0: partition along with it?

I guess so - afair you can call the partition DH0: and set WB_2.x as the label. You can run 3.x from it as well (provided there's a 3.x Kickstart file).

Quote
- Do I need a WB_1.3: partition if don't want to boot to 1.3?

I don't think so.

Quote
- I know the Super Kickstart files need to be in WB_2.x:devs/kickstart.  I assume "kickstart" needs to be a drawer containing the file?  If so, does the filename matter?  Or is the file actually called "kickstart" and located in WB_s.x:devs?


Nope. The filename needs to be "WB_2.x:devs/kickstart". The 1.4beta "boot ROM" is pretty dumb.
 

Offline KremlarTopic starter

  • Sr. Member
  • ****
  • Join Date: Jul 2009
  • Posts: 393
    • Show only replies by Kremlar
Re: help me restore my newly acquired Amiga 3000
« Reply #16 on: January 04, 2012, 08:34:25 PM »
Thanks for the reply!  According to the documentation I found with the MakeSuperDisk.lha utility it has to be the device name and not the volume label:

If you hold down both mouse buttons after you switch on the A3000 you
will be prompted to choose the operating system version to use. You can
either bootstrap Kickstart 2.x and Kickstart 1.3 from hard disk or from
floppy disk. If you don't hold down any mouse buttons the boot ROMs will
bootstrap the Kickstart from hard disk, using the partition with the
highest boot priority. Normally, this is the Kickstart 2.x boot partition.
   The hard disk partitions must be named "WB_2.x" and "WB_1.3" (note:
these are devices names like "DF0", *not* volume names) and the Kickstart
files must be in "WB_2.x:devs/kickstart" and "WB_1.3:devs/kickstart". The
partitions must be formatted either in standard filing system or fast
filing system format. You *cannot* bootstrap from hard disk drives that are
formatted with the international flavours of these filing systems or with
the directory caching filing system. When you make the choice to bootstrap
the operating system from hard disk, the Kickstart bonus code will disable
the "other" boot partition, i.e. if you choose Kickstart 2.x the "WB_1.3"
partition will be made invisible (and the other way round).
   If these Kickstart files and partitions are unavailable, you will only
have the option to bootstrap from floppy disk. This is the only option you
have after you replace the original hard disk drive with a "fresh" drive.

Now comes the tricky part. If you choose to bootstrap the operating system
from disk, the Amiga will no longer boot from the "WB_2.x" or "WB_1.3"
partition until you switch off the machine. You *have to* boot the
Workbench from floppy disk.

 
I guess my last concern is paritioning.  When this was new, were their multiple partitions?  Like a small WB_2.x: and small WB_1.3: PLUS a standard DH0:, or was the drive just divided in half with a kickstart on each half?
 

Offline AmiDude

  • Hero Member
  • *****
  • Join Date: Oct 2005
  • Posts: 903
    • Show only replies by AmiDude
Re: help me restore my newly acquired Amiga 3000
« Reply #17 on: January 05, 2012, 09:21:57 AM »
Quote from: Zac67;674342
The 1.4beta "boot ROM" is pretty dumb.


It's not as "dumb" as you might think. I've had an A3000 with 1.4 boot ROMs for years
and have had lots of fun with it! There where 3 partitions on it: wb_1.3: with OS/WB 1.3 and wb_2.x: with OS/WB 3.1. The other partition was for apps, games and music..
Now, most of the time I booted right into OS/WB3.1, but now and then, I booted (for compatibility and nostalgic reasons) into OS/WB 1.3. It works just like a build-in KickROM switch and therefore has a big advantage.
So, after all not as "dumb" as you think, huh?!
« Last Edit: January 05, 2012, 10:00:10 AM by AmiDude »
 

Offline KremlarTopic starter

  • Sr. Member
  • ****
  • Join Date: Jul 2009
  • Posts: 393
    • Show only replies by Kremlar
Re: help me restore my newly acquired Amiga 3000
« Reply #18 on: January 07, 2012, 04:22:49 AM »
Regarding my boot issue with no SCSI drive attached, according to one site it's a bug in my board:
 
rev 7.0
no SCSI termination is mounted on the motherboard, just sockets for three 8 pin resistor packs
cannot boot without at least one SCSI device attached
 
From here:
http://amiga.resource.cx/mod/a3000.html
 

Offline KremlarTopic starter

  • Sr. Member
  • ****
  • Join Date: Jul 2009
  • Posts: 393
    • Show only replies by Kremlar
Re: help me restore my newly acquired Amiga 3000
« Reply #19 on: January 11, 2012, 01:53:06 AM »
So, I ended up buying an SCSI CF card reader + PCMCIA adapter + 2GB CF card, 3.1 ROMs and upgraded SCSI chip (AMD version) from www.a4000t.com (mechy on this forum).
 
- First of all, prompt and professional shipping and service.
- Second of all, great products.
- Third of all, VERY reasonable prices.
- Fourth of all, tremendously helpful - well above and beyond what I'd expect in my wildest dreams! He was shooting emails back and forth with me in the late hours trying to help me get up and running. Can't say enough, highly recommended.
 
The 3.1 ROMs I got were ROM replacement chips - it turns out they would not work in those 2 open ROM sockets next to my ROM tower. I ended up using a steel wire (twist tie with the plastic removed) plus my soldering iron to heat/melt the pins stuck in those sockets and remove whatever I could. Once I did that I got the new 3.1 ROMs in there and was free of the ROM tower!
 

 

 
I also had to make some repairs to the LED board which seems to get damaged when the case is closed and bumps into it. I'm not very good at soldering at all, so this was a task. The traces on the board looked damaged, probably from too many amateur soldering attempts, so I ended up soldering wires from the motherboard connector coming into the board directly to the LEDs. I also am keeping the screw a bit loose so the board will wiggle a bit when the case is slid against it, hopefully preventing future damage. So far as good!
 
I also cleaned up the battery corrosion as best I could (vinegar, baking soda, toothbrush, alcohol, and clear nail varnish), then installed a coin battery (with diode) I had purchased on eBay.
 

 
Finally, I did my best to resolder the flicker fixer adjustment back onto the motherboard. Again, well beyond my soldering skills but it seems to be working OK after a lot of messing with it. I dropped some hot glue on it as well to help keep it in place. I've given it the wiggle test with my finger and it seems solid!
 

 
 
Here is my new SCSI chip:
 

 
 
I took the SCSI terminating resistors from the old hard drive I replaced and installed them on the 3000's motherboard.
 
I installed the CF card reader from Mechy in the 2nd floppy bay since I felt it was too crammed in the hard drive bay, if I could have gotten it to fit at all. I used velcro to secure it to the bay since the screw holes did not align.
 
One catch was that AmigaOS 3.1's HDToolbox would not correctly identify the 2GB CF card I got from Mechy or a 512MB one I had kicking around when inserted directly into the CF card slot. When trying to read information it errored out like this and saw it as a 20MB drive:
 

 
I had to install it in the card reader's PCMCIA slot with the PCMCIA converter that I also got from Mechy, and could then partition and format it properly. I then installed AmigaOS 3.1, then moved it back into the normal CF card slot and it seems to be working fine. The PCMCIA adapter juts out quite a bit from the CF card reader, and would not fit entirely inside the case, so I'm glad I was able to eliminate it after partitioning and formatting.
 
So, I now have my Amiga 3000 pretty much up and running! I'm awaing a 3000 floppy eject button that I ordered from here:
 
http://www.shapeways.com/model/310385/amiga_3000_disk_drive_eject_button.html?gid=ug96598
 
Other than that I hope to do a bit of retrobrighting and the system will be complete!
 
On a side note, are there any advantages to using AmigaOS 3.5 or 3.9 on this Amiga as-is? Any downsides to it?
« Last Edit: January 11, 2012, 01:55:08 AM by Kremlar »
 

Offline KremlarTopic starter

  • Sr. Member
  • ****
  • Join Date: Jul 2009
  • Posts: 393
    • Show only replies by Kremlar
Re: help me restore my newly acquired Amiga 3000
« Reply #20 on: January 11, 2012, 02:00:19 AM »
Here is the system as it stands now:

 

Offline touringsedan

  • Jr. Member
  • **
  • Join Date: Jan 2011
  • Posts: 50
    • Show only replies by touringsedan
    • http://nefertem.org
Re: help me restore my newly acquired Amiga 3000
« Reply #21 on: January 11, 2012, 02:12:46 AM »
Awesome Restore!

I bought an A3000D/16 last month and have been busy restoring it as well.

Also bought the SCSI CF reader from Mechy at a4000t.com and had the same excellent experience with him.

Just installed an A3640 3.1, 16MB of Zip Ram, Cybervision 64/3D, AD516 Sound Card and a Ariadne network adapter, Super Buster 11.

Running WB 3.9 w/BB4 installed and its running pretty awesome at this point.

Going to keep watching for a good 68060 with RAM/SCSI expansion onboard to max it out, but as it stands now, I am very happy.

Adding a 128MB ZorRam right now to give me the extra needed memory until I can find a perfect fit accelerator.

To keep me busy, I am seeking a last run of the MC68040 40Mhz as my current one is fine, but would like it to run cool especially in the A3000D's confined internal space.

Anyway, glad to see you got her up and running!

-Allen
 

Offline KremlarTopic starter

  • Sr. Member
  • ****
  • Join Date: Jul 2009
  • Posts: 393
    • Show only replies by Kremlar
Re: help me restore my newly acquired Amiga 3000
« Reply #22 on: January 11, 2012, 02:21:01 AM »
Wow, your system sounds great!  More than I intend to do with mine (for now).  I'm keeping my eyes open for a 4000 however.  Though this 3000 has sentimental value to me, the 4000 was the last Amiga I owned and I'd like to own another.
 

Offline KremlarTopic starter

  • Sr. Member
  • ****
  • Join Date: Jul 2009
  • Posts: 393
    • Show only replies by Kremlar
Re: help me restore my newly acquired Amiga 3000
« Reply #23 on: March 05, 2012, 12:11:32 PM »
Wanted to update this thread a bit.  I ended up getting a fantastic deal on a 4000T, which I detailed in another thread, so decided to move this CF card reader to that machine.  Instead I ended up moving the 1.2GB Quantum SCSI drive out of the 4000T and put it in this 3000.
 
After replacing the battery I found it only lasted a couple of days.  Checked the voltage and it was very low (~1.5v I believe).  I assumed it was simply a bum battery and replaced, but sure enough the new battery only lasted a couple of days as well.
 
I did some searching and found a user with a similar issue from way back in 2006 and he said his problem ended up being a diode on his 3000, D191.  I did have a lot of battery corrosion around D190 and D191, so I took a shot and replaced both diodes (1N4148).  It seems to have cured the issue, no battery loss in about a week!
 
I also added a HD floppy drive from a flakey 3000T I ended up acquiring.
 
While doing final assembly on this 3000 I made a big mistake - I offset the SCSI cable to the right by 1 set of pins and did not notice until I tried to power it on.  I then started experiencing flakey SCSI & boot issues.  With the help of Mech (www.a4000t.com) over IRC he helped me determine I had no termination power (check SCSI cable pin 26 for 5V).  This lead to a possible bad diode at D800, which just happened to be the same type of diode I had just replaced so had extras!  I replaced the diode, which he informed me was actually backwards on my board, and everything was good to go.  Crisis averted.
 
Anyway, this 3000 is now closed up and I hope to start using it soon.  Just wanted to cap off this thread (for now!).