Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: hektic on April 21, 2009, 09:56:08 PM
-
Hi!
I've just got an amiga 4000 which has Cyberstorm Mk1 060
the CDROM in it is connected to a buddha card. the HD that was in it is completely dead so i'm stuck trying to get OS3.9 on :(
I've created a 3.9 emergency disk from my desktop a4000 but that has a cyberstorm Mk2 and the CD drive is connected via scsi so I wasn't expecting it to go smoothly.
....... it didn't ......
When I boot the emergency disk on the new machine it complains it can't see cyberscsi. I thought it might see the IDE cdrom by default but it didn't so I tried connecting the SCSI cdrom from my other machine into the scsi port on the mk1 but it still complains.
What can I do to get OS3.9 on here as i've been trying all day!!! ?
If there is a guide to doing a fresh install with an 060 let me know please :)
Thanks
-
Afraid not.. Looks like you are going to have to sell that 060 to me cheaply :)
I am sure other more knowledgable than me will respond but I had never touched WinUAE before this weekend and I somehow managed to get os3.9 installed on a 40gig ide drive. I would assume you could install 3.9 with WinUAE on an IDE drive then install it in your 4000 then transfer the files from ide to your scsi drive.
-
Hey! how did you get the IDE drive formatted to RDB ... can you remember how you did it? (did you do the whole process using just WinUAE?) coz I did try to get a blank drive installed under WinUAE but couldn't get it recognised.
most guides show you how to setup using a hardfile etc but not a real blank ide.
Thanks!
-
the CDROM in it is connected to a buddha card
Put the emergency disk back into your deskop A4000 and edit Devs/DosDrivers/EMERGENCY_CD with a text editor.
Look for the lines reading Device=xxx and Unt=nnn.
For the unit number use one of these, depending where the CD drive is connected to:
primary master = 0
primary slave = 1
secondary master = 2
secondary slave = 3
The device name depends on whether there are devices connected to the onboard controllers of the A4000. If there is nothing connected to the onboard controllers, use scsi.device. If there is at least one device connected to the IDE *or* the SCSI controller (not both), use 2nd.device and if devices are connected to both the IDE and the SCSI controller of the A4000, use 3rd.scsi.device for the Buddha. Speaking only about IDE and SCSI on the A4000 mother board, not about the Cyberstorm SCSI. The CyberSCSI has its own driver which does not influence the name of the Buddha driver.
Bye,
Thomas
-
Thanks Thomas,
I'd like to run it with IDE devices only:
I've got the HD connected as primary master to the onboard IDE controller on the A4000.
I've got the IDE CDROM drive (primary master) connected to the IDE buddha zorro card.
Will the boot disk be able to see the CDROM drive connected to the buddha card without loading additional drivers?
If it will see it what settings should I try for this setup?
Thanks
-
the way i did it was to install OS 3.1 off floppy. I then installed the drivers for my fasATA ( its like your buddha) which came with a CD device driver and Cd Filesystem. You should have a device driver floppy for the buddha and you can get a demo of IDEFix off aminet to recognise the IDE CD on the buddha if you don't have a CD Filsystem for the Buddha. Then stick your OS 3.9 CD in and install OS 3.9, then the boing bag updates. You can get rid of the demo version of IDEFix as OS 3.9 has its own cd filesystem and ide drivers.
-
Will the boot disk be able to see the CDROM drive connected to the buddha card without loading additional drivers?
Yes, the Buddha has a firmware ROM which contains the driver.
Bye,
Thomas
-
Just found the installation software here: http://amiga.resource.cx/exp/buddha
After looking at it, it should work as I described. If (2nd./3rd.)scsi.device does not work, you could try buddha_atapi.device instead.
Bye,
Thomas
-
Install it on winuae:
"Before you begin you need to unlock WinUAE's HD safety checks which will prevent you from partitioning and formatting the HD otherwise. To do this you need to edit the WinUAE shortcut icon and add -disableharddrivesafetycheck after winuae.exe. Make sure you put a space between the .exe and -."
http://wiki.classicamiga.com/Installing_a_large_Harddrive_(4GB_or_larger)
-
Thanks guys will try to get it going by editing the emergency disk, if that doesn't work i'll go back and try giving WinUAE another go.
-
Thanks guys, I got OS3.9 on eventually! :)
I got it going by putting the CDROM onto the Amiga Mainboard IDE connecter as slave to the HD.
I'm now having problems with the Zorro cards....
It has a picasso 4, Ariadne net card and the buddah card connected to the mainboard by a MicroniK A4000 6960.
I installed the drivers for both the video and network card but when OS3.9 boots it complains it cant access the two resources.
Am I missing a step or does it sound like the Micronic board could be faulty? (I've reseated everything several times)
I got the drivers from amiga resource site.
Thanks again!
-
when OS3.9 boots it complains it cant access the two resources.
Please quote the exact error message. Or post a hardcopy.
Try to insert and install one board after the other.
Check early-startup menu if the cards are listed there.
Run ShowConfig and see if the cards are listed.
Micronic board could be faulty?
IMHO the Micronik board is of low quality anyway. Try to get hold of a Mediator4000 instead. It replaces the Micronik board completely and offers working PCI slots in addition.
(Note that I changed from a Micronk tower+board to a Mirage tower+board, so I cannot tell if the Mediator board fits into the Micronk tower mechanically. But IMHO it should.)
-
I've taken out the network card and the buddah card and it now see's the the video card. I can't get any output from it though it will not allow me to change the resolution.
Thanks for getting me this far I think i just need to read up on how to configure it, the cybervision in my other 4000 installed without issues.
When i plug the network card in and boot up workbench loads and then the mouse pointer freezes!?! must be some sort of IRQ conflict?
I'd love to get a mediator pci expansion but can't really justify the cost at the moment, i'm hoping the SAMS drop in price so I can take a look @ OS4 :)
Thanks for your help guys!
-
What exactly did you install for the Picasso IV card? You need only to install P96 which can be found here (http://aminet.net/package/driver/video/Picasso96).
-
hmm... I installed this
Verstion 1.4 from this site (http://amiga.resource.cx/exp/picasso4)
I've been away for the weekend so i've not had time to mess with it any further.
Is 1.4 from this site ok?
Thanks!
-
It's dead old, Aminet has at least 2.0.
-
OK thx, will try the latest drivers and see what happens :)
-
Guys, got the PicassoIV working now :)
When I change the resolution it comes out on the TFT ok but when I reboot it doesn't seem to save the settings after rebooting it.
Which file should I modify to get the resolution to stay or have i got something configured incorrectly.
I'm using screenmode in prefs to select the res.
Thanks again!
-
Use "Save" button instead of "Use" to make the change permanent.
If you did and it didn't work, make sure that Sys:Prefs/Env-Archive/Sys/screenmode.prefs is not write protected.
Bye,
Thomas
-
Sorted! I deleted that file rebooted and now it saves OK. Thx!
I thought these picassoIV's had a flickerfixer in them? I'm setting the resolution to 1024x768 and it shows as interlaced only.... the picture on the my TFT seems "interlaced" to me.
I went into picasso96mode and tried testing it with interlace unticked but the tft then can't display the image.
maybe i'm expecting a little to much from the Picasso?
-
I went into picasso96mode and tried testing it with interlace unticked but the tft then can't display the image.
Check the frequencies which are shown at the bottom of the page and make sure that they are still inside the monitor's specs. Deactivating interlace doubles the horizontal frequency. You have to decrease the pixel clock accordingly so that the frequency gets back into the supported range. However, changing the pixel clock influences both, the horizontal and the vertical frequency. So you probably have to experiment with the sync values, too, to stay inside the specs.
Bye,
Thomas
-
Thomas your a star! Thats sorted it now it looks great!
turned interlace off and then adjusted pixel clock until hor & vert freq's were at 60 & 71 hz
Looks perfect now.
Thanks!!