Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: amigasociety on November 27, 2011, 07:07:05 PM
-
Picked up a non working A4000T yesterday. Was told it did not boot and they believed it to be a software harddrive issue.
Connected it to a 1080 monitor today and tried to boot it. Floppy whirs, hard drive live flickers. CD light comes on sometimes, all the while I have a purple raster on the screen.
Eventually the screen goes dark and nothing.
Tried without 3.1 floppy and with it.
Looked inside, don't see anything burnt up and all looks clean. Has a 68060 board with ram in it. Noticed NO ram in the motherboard slots. Does it need some to boot? Only ram was on 68060 board.
They also have some Toaster 4000 card inside.
Before I go and pull the videotoaster card and reseat the 68060, any other advice for a newbie?
Does the purple raster tell me anything and then blank video afterwards?
Thanks
TJ
-
Try reseating the KS chips. Make sure the CPU card is well seated also..
-
You need at least the 2mb of Chip RAM to be installed. It is okay to have the other motherboard RAM removed and only use the RAM on the 060 accelerator card, but you must have the 2mb of Chip RAM installed (AFAIK).
-
all the four ram slots are empty on my A4000T yet I had 2mbs of chipram. (when it was working 7 years ago :( )
-
I would remove all the expansion cards and hard drives first then reseat the kickstart chip.
All you need is the cpu, chipram and the floppy. If I remember correctly purple lines means the kickstart isnt executing properly.
-
I would remove all the expansion cards and hard drives first then reseat the kickstart chip.
All you need is the cpu, chipram and the floppy. If I remember correctly purple lines means the kickstart isnt executing properly.
If the KS chip is bad, can one boot the A4000T if I find a kickstart floppy?
What version of kickstart floppy would I need if that is the case?
Or will it work from KS chip only?
tj
-
No, kickstart is loaded from chips.
Just remove the zorro cards, reset the 060 card...should boot to insert workbench screen.
You will need a workbench disk with the 060 libs and the 040 fakea nd real libs.
-
No, kickstart is loaded from chips.
Just remove the zorro cards, reset the 060 card...should boot to insert workbench screen.
You will need a workbench disk with the 060 libs and the 040 fakea nd real libs.
Sounds like I need to join the SACC club and bring the 4000T to the next meeting so we can see about getting it booted.
I don't have any idea on how to make a workbench disk with 060 libs and 040 fakea. :angry:
TJ
-
Joining SACC is always a good idea. The members always help fellow amigians.
just copy the small 040lib and real 040lib and the 060lib to libs:
available on several sites aminet, etc
It might help to id the best 060lib for your board (phase5 or what?)
next meeting dec 5th (I think) check sacc.org or call chuck
-
Sounds like I need to join the SACC club and bring the 4000T to the next meeting so we can see about getting it booted.
I don't have any idea on how to make a workbench disk with 060 libs and 040 fakea. :angry:
TJ
reseat the roms and accelerator board. remove any cards other than the 060.check the 060's jumpers to be correct and also check the 4000t motherboard jumpers.
check the power supply with a voltmeter for +5 and +12v.it should be close when its powered(you can check for voltages at a hd connector)
mech
-
all the four ram slots are empty on my A4000T yet I had 2mbs of chipram. (when it was working 7 years ago :( )
I guess I am thinking of the A4000D motherboard that has a 2mb Chip RAM simm and did not realize that the A4000T motherboard did not have a Chip RAM simm slot.
I sold my A4000T last year and did not open it up much while I had it.
-
Hi,
I would pull the video toaster, then I would leave the A4000 on for at least a half hour, then try rebooting. If the A4000 has been sitting for a while without being turned on, somethimes it has a hard time starting (at least mine does) after I leave it turned on for a while turn it off then turn it on, it starts right up. What mine usually does it shows me a purple stripe going vertically down the screen then goes black. After I leave it on for half an hour (or more) then turn it off, then back on it seems to take the purple stripe and then waves it, then turn I hear the familiar click of the hard drive looking for files.
This could only be my A4000, I really don't know.
smerf
-
Hi,
I would pull the video toaster, then I would leave the A4000 on for at least a half hour, then try rebooting. If the A4000 has been sitting for a while without being turned on, somethimes it has a hard time starting (at least mine does) after I leave it turned on for a while turn it off then turn it on, it starts right up. What mine usually does it shows me a purple stripe going vertically down the screen then goes black. After I leave it on for half an hour (or more) then turn it off, then back on it seems to take the purple stripe and then waves it, then turn I hear the familiar click of the hard drive looking for files.
This could only be my A4000, I really don't know.
smerf
Wow.. your A4000T is hard to turn on sometimes. You have to warm her up first :o
-
Wow.. your A4000T is hard to turn on sometimes. You have to warm her up first :o
Hi,
Only after she sits for a while, then she has trouble starting, have to let her warm up, then push her buttons don't yah know.
smerf
-
http://bboah.claunia.com/a4000tc.html, "workbench.library was moved from ROM, supplied on the Workbench disks and is loaded from LIBS:"
I do not think this is your booting problem but is something to consider when trying to boot from floppy when trying disconnecting drives to find your problem.
-
Sent you a PM...
-
Does it have the disks module ? If not it won't boot.
-
Hi,
... I would leave the A4000 on for at least a half hour, then try rebooting. If the A4000 has been sitting for a while without being turned on, somethimes it has a hard time starting (at least mine does) after I leave it turned on for a while turn it off then turn it on, it starts right up.
:) Same thing with my A4000T.. If its been unused for a couple of months or so, it just won't boot up properly. Leaving her to warm up for a while, then starts like nothing ever happened.
-
:) Same thing with my A4000T.. If its been unused for a couple of months or so, it just won't boot up properly. Leaving her to warm up for a while, then starts like nothing ever happened.
Its been my experience this is usually caused by bad contact in the cpu slot.carefully adjusting the pins with a fine sewing needle can fix that and use some quality contact cleaner. If you want to fix it permanently,after cleaning, install some proper standoffs instead of plastic pegs and use screws to keep the accelerator in. seems the heating/cooling cycles can gradually work the accelerator out a bit to cause the trouble you mention.
Mech
-
Hello amigasociety,
Try with everything disconnected except modules (video/audio & disk) and the 060 card. Remove the 060 card to verify the jumpers below it, I think they should be on the EXT position, if not you can try on the INT position but I'm almost sure it should be EXT.
Do not worry about RAM on the motherboard. The machine has chip ram soldered to the motherboard so no problem there.
Verify the KS chips to see if they are well seated (I got one as non-working and it had one pin outside of the socket). Also, the chips should be version 40.70, I think that's printed on the top.
The machine will take a little while since it has no HDs or Floppy, but if everything is OK, it should come up to the "Insert WB Disk" animation.
Good idea also to check for voltages but do as the previous advice and measure it from one of the molex connectors, or to be completely sure about voltages reaching the motherboard, disconnect the power from the motherboartd itself and measure from that connector (http://www.playtool.com/pages/psuconnectors/connectors.html#oldpc).
Good luck with your A400T! :)
efrenmgp
-
OK, update #1
Toaster 4000 Card removed, still no boot, same screens as before.
Unpluged SCSI hard drive but left CD and Floppy connected and I now get a new screen.
Am I correct this is the Kickstart Screen asking for Workbench or is this a screen asking for and not finding Kickstart?
I seem to remember a hand asking for workbench.
Anyway, see attached picture.
I put in the floppy drive both the stock A4000T Install and also Workbench 3.1 floppys, the drive whirs a moment, goes back to this same screen with a floppy going into flopy drive.
By the way, where is this kickstart chip so I can push it down and make sure it is seated.
tj
(http://gallery.me.com/macsociety/100154/A4000Tscreen/web.jpg)
-
Am I correct this is the Kickstart Screen asking for Workbench or is this a screen asking for and not finding Kickstart?
...
I put in the floppy drive both the stock A4000T Install and also Workbench 3.1 floppys, the drive whirs a moment, goes back to this same screen with a floppy going into flopy drive.
That is the kickstart screen asking for a WB disk, so good news! the machine boots!! :banana:
Now for the second issue, the floppy disks not booting, it can be that either the disks are damaged (or not bootable) or the floppy drive is damaged.
Do you have another computer to test those disks on it and if they work, exchange the floopy drives and test again on the A4KT?
Regards,
efrenmgp
-
That is the kickstart screen asking for a WB disk, so good news! the machine boots!! :banana:
Now for the second issue, the floppy disks not booting, it can be that either the disks are damaged (or not bootable) or the floppy drive is damaged.
Do you have another computer to test those disks on it and if they work, exchange the floopy drives and test again on the A4KT?
Regards,
efrenmgp
The running Amigas I have is a newer SAM 440ep based system (no floppy drive) and an CD32 (no floppy drive) and a Amiga 1000 with two floppies, internal and external.
But, I am guessing the stock 4000T floppies I have will not read in an ancient A1000, will they?
I do have that 2nd Amiga (untested) I picked up, a A4000D based HUMONGUS case beast that has a drive in it but no idea yet if she boots or runs.
But, other than hearing the drive whir and seeing the light come on, that is all I can get.
How about from AmigaDOS.... since I can boot to with no startup sequence.... what command do I send to it to read the floppy drive? Could I do that to see if she can read the drive?
tj
-
The running Amigas I have is a newer SAM 440ep based system (no floppy drive) and an CD32 (no floppy drive) and a Amiga 1000 with two floppies, internal and external.
But, I am guessing the stock 4000T floppies I have will not read in an ancient A1000, will they?
I do have that 2nd Amiga (untested) I picked up, a A4000D based HUMONGUS case beast that has a drive in it but no idea yet if she boots or runs.
But, other than hearing the drive whir and seeing the light come on, that is all I can get.
How about from AmigaDOS.... since I can boot to with no startup sequence.... what command do I send to it to read the floppy drive? Could I do that to see if she can read the drive?
tj
I'm not sure if the 4000T disks will at least boot on the A1000. Surely WB won't load buy maybe you'll end up with some error and that would mean that the floppies are bootable so the failure would be on the floppy drive itself. You could take the floppy drive from that 4KD machine and test.
Question: If you leave the 4KT turned on with no floppy inside the drive, can you hear the constant clicking every second or so?
Other thing you can do is prepare a new floppy on the A1K, format it and run the Install command to make it bootable. In a shell window type Install DF0: and follow the prompts. Then use that disk on the 4KT, it should boot to a Shell window, that will tell you that your floppy drive is OK and then the floppies are either bad or not bootable.
-
ffs system disks won't boot with anything below kickstart2.0
You'll just hear three drive clicks and nothing else.
-
ffs system disks won't boot with anything below kickstart2.0
You'll just hear three drive clicks and nothing else.
Thanks I wasn't sure of that :)
So using the A4KT floppies with the A1K won't tell you anything useful :(
Regards,
efrenmgp
-
I think it's the battery. You need to remove the battery (if you haveb't done it yet, it's dangerous to leave it there) and install a new battery (preferably mod it so that you can use safe coin batteries)
After that you need to boot from an ide harddrive, run the report+ tool from aminet and save some bits to the NVRAM.
It may sound a bit complicated (well.. it does) .. It's either that your scsi hdd is defective or it's the problem I described about the battery. Also you probably need a new floppp drive. First check its cables.. Also there should be some kind of add on adapter fitted on the disk module of A4000T. It could be missing or there could be a problem with that.
-
Good news!!! She boots from floppy.
:-P
Stole the floppy drive from the A4000 I also acquired and she boots from the A4000T Workbench 3.1 floppy.
So, I think we have a winner here.
Before I go further, I now have to find someplace that sells HD Floppies so I can make dups of the A4000T floppies.
All I need now is to screw them up.
Who in town will have any floppies (hehehe).
Anyway, I re-connected the SCSI drive, it is seen, used HDTools and formated the drive, started an install (using my master A4000T floppies) and during install it came back with a message my A4000T Workbench 3.1 is write protected. Which it is, I made sure it was.
Worried that I might screw up my one and only floppy, I halted operation.
Tell me, does the installer floppies need to be in write mode to allow me to install?
I find that odd.
Anyway, time to find some floppies and learn how to make some dups.
tj
-
BTW, what floppy disks do I need. The stock A4000T have a HD on the covers. One side is taped off. My guess I can buy any old HD floppy and tape off and use them?
TJ
-
All 4000Desktops and early 4000towers came with hi-density drives.
In amiga speak that was 1.76k (1.44 for pc's)
Until they ran out of that special drive.
BTW, the 4000T was also the only Amiga that does not have an external connector for an outside floppy drive.
Other amigas came with 88ok floppy drives. Which as you discovered can be swapped.
You can still find DD floppies or use HD's with the second hole covered trick.
m
-
On my Escom A4000T (Commodore produced only 200 A4000Ts) there is an addon thats attached to the Disk Module and supported by silicon. I've been told that I would have to remove this addon if I wanted to remove the standard 880k floppy drive and attach a 1.76m floppy drive.
I recently bought one and will install that on my A4000T.
-
Radio Shack had a deal on 10 pack of HD floppies. $1.99 so I purchased 2 boxes, all they had left.
Funny thing is the sign neat the floppies on the shelf said $9.99.
Anyway, making copies of the A4000T Floppies as we speak.
Will let you all know how install goes later.
tj
-
Man I feel sooo close but can't seem to get Workbench 3.1 installed on the internal SCSI drive to boot.
I am able to boot to the Workbench 3. fine, made copies of all floppies, boot the system from the Workbench Floppy, use HD Tools and made 3 partitions (500MB, 500MB, 1000MB), then rebooted from Floppy again and formatted the HD partitions naming them Workbench, Work, & Storage.
While booted from Workbench floppy insert the Install floppy and did a Intermediate install (novice would not work as it tried to install to the floppy and not let me select the Workbench bootable hard drive partition). Install seems to go fine. Reboot and I get the following error when it tried to boot from the HDD.
In red letters:
Error 8000 000B
Tasj 08025BD0
Hold Left Mouse Button to reboot and it keeps going back to that until I put the floppy in.
What is it on the 3.1 floppy disk that is not transferring over to the hard drive that allows it to boot?
Remember this is a 68060 Cyberstorm MKII. Obviously enough is on the floppy to boot so why not the install it just did?
TJ
-
You must boot from the "Install 3.1" disk and install AmigaOS3.1 that way. Do no boot from Workbench3.1 disk and install AmigaOS3.1 ;)
If you boot from your Workbench 3.1 disk, it will become the SYS: and it is something you don't want.
When creating partions, make sure the first partion (leftmost) is "bootable" and definitely smaller than 2gb. Make it fastfilesystem and don't forget to install fastfilesystem on the RDB as well.
Leave the logical names as DH0: DH1: DH2: (or HD0: HD1: HD2:) you can rename the "labels" as Workbench Work , etc...
If the above gives you the same result, there could be an incompatibility with the stock 68040.library and the setpatch command with your accelerator.
try renaming the 68040.library and 68060.library inside the libs directory to 68040.library.bak and 68060.library.bak (not the floppies)
turn on the machine and hold two mouse buttons.
boot with no startup-sequence
type the following:
---------------------------------------------
sys:
libs
dir 68#?
---------------------------------------------
you'll probably just see the 68040.library there I think.
rename it with the command:
---------------------------------------------
rename 68040.library 68040.library.bak
---------------------------------------------
Wait 5 seconds for all disk activity to finish and reboot. (if you reset too soon after the drive writes something, you risk invalidating your fastfilesystem formatted partion and that's a bad thing)
You will need the three libraries that are needed by your 060 board.
http://amiga.resource.cx/exp/cyberstorm2
things that I "absolutely" needed to make my Amiga working properly: (with these disks, it felt like I could... CONQUER THE WORLD!)
1- AmigaOS3.1 floppies
2- A TCPIP stack (Miami and later MiamiDX on floppies (with the three keyfiles now on aminet) were what I had)
3- An external dialup modem with correct cable that I could use to go online and download stuff.
4- (optional: TERM ... a terminal program that allowed me to "ahem" download stuff :) it was so much fun. )
5- An old version of AWeb or IBrowse so that I could download stuff.
6- AsimCDFileSystem or CacheCDFilesystem on floppies to configure my CDROM
7- A floppy with DiskMaster3
8- a floppy with commands like lha, latest setpatch from aminet.
9- the correct 68060 and 68040 libraries for my card on a floppy.
10- IdeFix on a floppy (I'm still not sure if I actually needed this)
...
11- Many years later, AmigaOS3.9 CD :)
After installing AmigaOS3.1 and booting properly from the harddrive with no floppies inserted (if it crashes, try renaming the 68040 and 68060 libraries like I told you and try again) you'll find a thing named PC0 in you Storage/Dosdrivers directory. If you doubleclick that and insert a pc formatted floppy (I think you have a high density floppy drive so your Amiga can read 1.44mb pc disks), your amiga is able to read its contents. This is how you can transfer files from your PC to your Amiga. The CrossDos version that came with AmigaOS3.1 is old and it only supports 8 character long filenames. You'll need CrossDos7
My Windows7 64 can not format floppies from its icon. I have to open a CMD and format using the dos command.
-
Whew, I got some work to do it appears. :roflmao:
Problem is, the A4000T will not boot from my Install Floppy, only the Workbench Floppy, so that is where my problem starts.
I know the floppy drive and floppy is fine, data is there and all, but my guess is there is something on the Workbench Floppy that the INstall floppy is lacking.
Not sure how I would get past that.
tj
You must boot from the "Install 3.1" disk and install AmigaOS3.1 that way. Do no boot from Workbench3.1 disk and install AmigaOS3.1 ;)
If you boot from your Workbench 3.1 disk, it will become the SYS: and it is something you don't want.
When creating partions, make sure the first partion (leftmost) is "bootable" and definitely smaller than 2gb. Make it fastfilesystem and don't forget to install fastfilesystem on the RDB as well.
Leave the logical names as DH0: DH1: DH2: (or HD0: HD1: HD2:) you can rename the "labels" as Workbench Work , etc...
If the above gives you the same result, there could be an incompatibility with the stock 68040.library and the setpatch command with your accelerator.
try renaming the 68040.library and 68060.library inside the libs directory to 68040.library.bak and 68060.library.bak (not the floppies)
turn on the machine and hold two mouse buttons.
boot with no startup-sequence
type the following:
---------------------------------------------
sys:
libs
dir 68#?
---------------------------------------------
you'll probably just see the 68040.library there I think.
rename it with the command:
---------------------------------------------
rename 68040.library 68040.library.bak
---------------------------------------------
Wait 5 seconds for all disk activity to finish and reboot. (if you reset too soon after the drive writes something, you risk invalidating your fastfilesystem formatted partion and that's a bad thing)
You will need the three libraries that are needed by your 060 board.
http://amiga.resource.cx/exp/cyberstorm2
things that I "absolutely" needed to make my Amiga working properly: (with these disks, it felt like I could... CONQUER THE WORLD!)
1- AmigaOS3.1 floppies
2- A TCPIP stack (Miami and later MiamiDX on floppies (with the three keyfiles now on aminet) were what I had)
3- An external dialup modem with correct cable that I could use to go online and download stuff.
4- (optional: TERM ... a terminal program that allowed me to "ahem" download stuff :) it was so much fun. )
5- An old version of AWeb or IBrowse so that I could download stuff.
6- AsimCDFileSystem or CacheCDFilesystem on floppies to configure my CDROM
7- A floppy with DiskMaster3
8- a floppy with commands like lha, latest setpatch from aminet.
9- the correct 68060 and 68040 libraries for my card on a floppy.
10- IdeFix on a floppy (I'm still not sure if I actually needed this)
...
11- Many years later, AmigaOS3.9 CD :)
After installing AmigaOS3.1 and booting properly from the harddrive with no floppies inserted (if it crashes, try renaming the 68040 and 68060 libraries like I told you and try again) you'll find a thing named PC0 in you Storage/Dosdrivers directory. If you doubleclick that and insert a pc formatted floppy (I think you have a high density floppy drive so your Amiga can read 1.44mb pc disks), your amiga is able to read its contents. This is how you can transfer files from your PC to your Amiga. The CrossDos version that came with AmigaOS3.1 is old and it only supports 8 character long filenames. You'll need CrossDos7
My Windows7 64 can not format floppies from its icon. I have to open a CMD and format using the dos command.
-
Picked up a non working A4000T yesterday. Was told it did not boot and they believed it to be a software harddrive issue.
Connected it to a 1080 monitor today and tried to boot it. Floppy whirs, hard drive live flickers. CD light comes on sometimes, all the while I have a purple raster on the screen.
TJ
I always had problems with the A/V module coming loose. It's on pin header connection to motherboard, which comes loose easily. Make sure that's tight and try again, if it goes good then hot glue it or something. But I don't remember this causing purple... Though I think kickstart screen has a purple background, maybe it's not getting to draw the disk? Check your RAM is tight fitting too. Wiggle any plugins and press them tight...
-
Whew, I got some work to do it appears. :roflmao:
Problem is, the A4000T will not boot from my Install Floppy, only the Workbench Floppy, so that is where my problem starts.
I know the floppy drive and floppy is fine, data is there and all, but my guess is there is something on the Workbench Floppy that the INstall floppy is lacking.
Not sure how I would get past that.
tj
The answer lies within your question. an Install floppy must be installed before it can be bootable. :P (never remove the write protection from your original disks)
-
The answer lies within your question. an Install floppy must be installed before it can be bootable. :P (never remove the write protection from your original disks)
What the heck do you mean by that statement? You mean it must be inserted inside the floppy drive, then I agree, but otherwise, I don't know what the heck you are writing about. An Amiga Install disk is always bootable, unless it is damaged, or there is a problem with the floppy drive.
I suggest giving the floppy drive a good cleaning and checking the Install floppy disk in another Amiga to see if it boots on another Amiga machine.
-
Yes, only my A4000T Workbench 3.1 Floppy boots this computer. The Install floppy does not although it is fully readable, copyable, I can see all the files on it, transfer to another floppy, etc....
The drive is reading and writing it appears fine.
I formatted floppies today and made copies of all my floppies so it seems to be running well.
tj
-
Yes, only my A4000T Workbench 3.1 Floppy boots this computer. The Install floppy does not although it is fully readable, copyable, I can see all the files on it, transfer to another floppy, etc....
The drive is reading and writing it appears fine.
I formatted floppies today and made copies of all my floppies so it seems to be running well.
tj
Well, if your Install floppy disk will not boot your A4000T, it either has something wrong with it, or it is not the correct Install floppy for an A4000T.
The 3.1 Install floppy for a A4000T is different than the Install floppy for any other Amiga computer.
If you downloaded these floppy images from the Internet, you probably don't have the one you need for the A4000T.
Sorry I can't provide more help, I am half asleep and can't think straight at the moment. Too much pasta for dinner dulls the brain.
-
amigadave:
He has the A4000T Workbench 3.1 disks and his A4000T 3.1 rom since it's not a Commodore one.
It seems like there's something wrong with his Install3.1 disk. So he needs to install an empty floppy disk and copy over the files from the original Install3.1 disk to that empty disk and rename the empty disk as Install3.1
-
Well, if your Install floppy disk will not boot your A4000T, it either has something wrong with it, or it is not the correct Install floppy for an A4000T.
The 3.1 Install floppy for a A4000T is different than the Install floppy for any other Amiga computer.
If you downloaded these floppy images from the Internet, you probably don't have the one you need for the A4000T.
Sorry I can't provide more help, I am half asleep and can't think straight at the moment. Too much pasta for dinner dulls the brain.
Mine are OEM Amiga floppies, not copies.
But yes, I guess it can be bad.
So, how can I buy another copy, downloaded to a Mac OS X machine, and somehow create a floppy for my Amiga?
I do have an older OS 9/X Cube with a USB floppy on it. Not really sure that would help of course.
Is there a way to go "around Workbench 3.1"? Meaning, jump up to OS 3.5 or 3.9 without having to install 3.1? Can I buy this someplace?
And if yes, do these newer OSes have 060 libraries or whatever is needed to install and make bootable a Cyberstorm 060 based A4000T?
My manual that comes with the Cyberstorm basically said you needed to install their software before installing the 060 card but I don't have that luxory anymore as I have no 040 to go back to. Not even sure that is the issue since my system boots from workbench A4000T floppy so.
Hey Sac Amiga group, any of you here reading this thread?
Any of you running A4000T?
I would like to bring the A4000T to your next meeting. :hammer::hammer:
tj
-
On my Escom A4000T (Commodore produced only 200 A4000Ts) there is an addon thats attached to the Disk Module and supported by silicon. I've been told that I would have to remove this addon if I wanted to remove the standard 880k floppy drive and attach a 1.76m floppy drive.
I recently bought one and will install that on my A4000T.
To address your earlier message, A4000T's have lithium batteries stock. they do not have the leakage problem of the earlier rev A4000's. the 4000T's lithium battery is just soldered in.
Some 4000t's had a small board plugged to the floppy pin header,it was just for using a pc floppy in them(many came with sony drives). later ones came with ugly hacked floppy cables instead of that little board. Any 4000T can use a High density drive, you just need a good cable that hasnt been hacked. no changes need to be made to the disk board other than removing that small adapter if its present.
Mech
-
Make a copy of your bootable Workbench disk and then erase enough files on it to make room so you can copy all of the files from the Install floppy disk to it and rename it to the same name of your Install disk. That should give you a bootable disk that has all of the Install files and allow you to do a proper install of OS3.1.
Hope this helps.
-
I know it sounds stupid but although AmigaOS 3.9 comes with 3.1 inside it, you still need to have 3.1 disks in order to install AmigaOS3.9 because you need to have a working cdrom :D
-
Make a copy of your bootable Workbench disk and then erase enough files on it to make room so you can copy all of the files from the Install floppy disk to it and rename it to the same name of your Install disk. That should give you a bootable disk that has all of the Install files and allow you to do a proper install of OS3.1.
Hope this helps.
Yyes. this should work too.. But you have to copy from icon menu I think. If you simply copy the files to an empty disk, it won't work.
-
To address your earlier message, A4000T's have lithium batteries stock. they do not have the leakage problem of the earlier rev A4000's. the 4000T's lithium battery is just soldered in.
Some 4000t's had a small board plugged to the floppy pin header,it was just for using a pc floppy in them(many came with sony drives). later ones came with ugly hacked floppy cables instead of that little board. Any 4000T can use a High density drive, you just need a good cable that hasnt been hacked. no changes need to be made to the disk board other than removing that small adapter if its present.
Mech
Maybe there is that dongle on this A4000T and it's causing problems with the Install disk and the high density floppy drive amigasociety is using?
Amigasociety: http://winuaehelp.back2roots.org/background/amigados.htm
Here are explanations of AmigaDOS commands which shall come in handy.
Also don't forget that you definitely need this for AmigaOS3.1 to function properly with you card: http://aminet.net/package/util/boot/SetPatch_43.6b
And this self extracting lha command to extract lha files: http://aminet.net/util/arc/lha.run
-
Mine are OEM Amiga floppies, not copies.
But yes, I guess it can be bad.
Hey Sac Amiga group, any of you here reading this thread?
Any of you running A4000T?
I would like to bring the A4000T to your next meeting. :hammer::hammer:
tj
sigh
Yes, several sacc members have seen your post.
Yes, you are welcome to come to the dec 5th meeting (as I posted several times before)
It's normally a shared holiday meet (after amiwest)
please refer to the sacc dot org page for location info
Please contact Chuck so he can arrange to have the help you need (ie ask the 4000T owner(s) to make an effort to attend)
(if you haven't brought all the items you need and no-one else has either...)tools, monitors, cables, disks, extras, etc...
Yes, we have 4000T owning members.
m
-
sigh
Yes, several sacc members have seen your post.
Yes, you are welcome to come to the dec 5th meeting (as I posted several times before)
It's normally a shared holiday meet (after amiwest)
please refer to the sacc dot org page for location info
Please contact Chuck so he can arrange to have the help you need (ie ask the 4000T owner(s) to make an effort to attend)
(if you haven't brought all the items you need and no-one else has either...)tools, monitors, cables, disks, extras, etc...
Yes, we have 4000T owning members.
m
I will have to see if I can find Chucks contact info on your page.
See you tomorrow.
Tj
-
It's there. Has been for years and years.
-
Thanks for Sacc-Guy and the SACC Amiga Club I now have a working A4000T from hard drive. Enjoyed 3+ hours of Amiga time last night as I joined their club for their Dec meet.
Was nice to meet people, learn Amiga, and come home with a running system.
Hands on help is always the best!
Ended up needing the special 060 library like some said allowed the hard drive to boot. So was close, real close, but having that helping and teaching hand guide things made it happen.
Now I have a better idea of how this all works.
Now it is time to play!
tj
*also thanks to those here that helped me. Without this community, I would be babbling on the side of the road with a nice A4000T being used as a seat to sit on. :hammer:
-
You're welcome.
m