Fresh 4000

[prowler]

Originally Posted by alexh

I don't think it's acceptable for senior members of EAB to give bad advice about kickstart ROM's that WILL work in A4000D if you follow the right installation procedure. Jebus you're all becoming version Nazi's

I'm sure that AmigaKit will be adding an extra line to their installation guide about installing wb.lib to your hard drive before upgrading ROMs.

My comment was not intended to be taken as advice, bad or otherwise. It was merely my personal opinion based on the events chronicled in this thread.

Originally Posted by amigakit.com

@prowler

We have three desktop A4000 Desktops in use here in the office. They all have 40.70 ROMs installed.

We clearly advise before selling 40.70 ROMs that the end user needs a version of AmigaOS with Workbench.library in LIBS: so how can it be "unacceptable" if we have not misrepresented the product before purchase?

Thankyou for clarifying your position on this.

I understood from the problem described by Dr. Dude when he powered up his A4000 for the first time following his upgrade that he wasn't aware of the requirement for the Workbench library on disk.

It seems to have been only his misunderstanding of your advice and his reaction to the consequences of it that caused me to gain that impression, and for that I apologize. It is only because I have a machine myself which I would like to upgrade, that I was so sensitive to the slightest signal that it might be problematic.

However, it is still my personal preference to seek a v40.68 3.1 ROM set for my A4000/40 desktop machine upgrade.

[Dr. Dude]

ok enough about the roms, my advice to amigakit, join in a basic WB disk complete whit the wb.lib
I wil build (or buy if i can find what i lookfor) a kickrom switch whit 40.68,40.70 and a extra space for a future one

I think i solved my wb.lib, as i am typing this WinUAE is running whit the HD that came out of the real A4000.

Time to fully reinstall the disk whit OS3.5, just to see what hapens in the amiga. To prepare for the flashcard

no catweasel needed

[FOL]

Originally Posted by Dr. Dude

ok enough about the roms, my advice to amigakit, join in a basic WB disk complete whit the wb.lib
I wil build (or buy if i can find what i lookfor) a kickrom switch whit 40.68,40.70 and a extra space for a future one

I think i solved my wb.lib, as i am typing this WinUAE is running whit the HD that came out of the real A4000.

Time to fully reinstall the disk whit OS3.5, just to see what hapens in the amiga. To prepare for the flashcard

no catweasel needed

No need to build a rom switcher, using 2 of our rom switchers will work fine, . just slap the 2 sets of kickstarts in accordingly and away you go, .

[Dr. Dude]

Originally Posted by FOL

No need to build a rom switcher, using 2 of our rom switchers will work fine, . just slap the 2 sets of kickstarts in accordingly and away you go, .

just for what you said i am going to build it... give me a break, 2 units
that is not my idea of "fitting" components, and it only gives room for 2 sets and not 3

softswitch is nice, but no thanks for me. I think i just use a switch on the power of the roms, pure hardware, maybe a simple jumper or something on a backplate. Not the idea to keep switching all the time

[Jope]

A kickflash and a supported CPU card is my choice for ROM switching in the A4000. Wire a switch to the jumper to en/disable it.

[Dr. Dude]

ok this is wiert, i wired the A4000 hd to my pc
cleared it, and installed 3.5
once i fit it in my A4000... nothing...it wil just keep a black screen
unplug it and after the usual 20 secs the insert disk screen

[prowler]

Did you retain the partitions when you wiped it in WinUAE?

[Dr. Dude]

no size was not good for win 3.5

i gave hd0 100mb
and hd1 the rest (412mb)
l had the HD set to IDE0
loaded up WB by disk and partitioned whit the tools
after that installed 3.1 / pre 3.5 / full 3.5

[prowler]

Did you specify scsi.device or uaehf.device when partitioning the drive with HDToolbox?

[Dr. Dude]

ok lost you there
interface = scsi
adres = 0
lin = 0
Drive type = UAE-IDE st3660A

[prowler]

When you run HDToolbox to partition a hard drive you need to give the name of the device which is used to access the disk. Using WinUAE, it should be either scsi.device (the default device which will be used by your Amiga when the drive is replaced in it) or uaehf.device (the device which is part of WinUAE and used primarily for partitioning hardfiles).

You should specify scsi.device when preparing a hard drive in WinUAE which you intend to replace in your Amiga when it is done.

So, which did you specify?

[Dr. Dude]

no selection there
but when i ask for icon info on Hdtoolbox

scsi_devive_name=scsi.device
scsi_max_address=6
Scsi_max_lun=7
Xt_name= xt

[prowler]

If that information is returned when you request icon info for HDToolbox in WinUAE, then the disk preparation should have been compatible with your Amiga.

Furthermore, your partition sizes do not require support for large IDE hard drives, so it is likely that the hard drive format is okay.

This makes it difficult to pinpoint what might be causing the problem.

[Dr. Dude]

its wiert, it just sits there, you head the HD starting on powerup, after that it does nothing, nor the disk drive

oh and vesalia has dispatched my order

guess its going to be trial and lots of error to get the HD running on the miggy

[FOL]

Just to update, I have been experimenting and even though I knew it would work, just thought I would try doing it a few different ways.

Everytime it worked flawless. So to use the 40.70 roms in an A4000D, you just need the workbench.library in the LIBS: folder.

Originally Posted by Dr. Dude

its wiert, it just sits there, you head the HD starting on powerup, after that it does nothing, nor the disk drive

oh and vesalia has dispatched my order

guess its going to be trial and lots of error to get the HD running on the miggy

Sounds like its going from bad to worse, .

[Jope]

;-)

KickInfo 1.2 © 1995 MJSoft -- analysing `Kick40070.A4000'
File size=080000, Ident=1114, Entry=00F800D2, Ver=40.70, ExecVer=40.10
IntSize=080000, Checksum=A580A2DE/A580A2DE
Kickstart ID: Kick40070.A4000

Modules:
F800B6 exec 40.10 (15.7.93)
F8370E alert.hook
F837C0 layers 40.1 (15.2.93)
F86976 wbtag 39.1 (20.4.92)
F86A38 audio 37.10 (26.4.91)
F87B08 scsidisk 40.20 (18.2.94) [A4000]
F8A5BC bootmenu 40.5 (17.3.93)
F8A5FC syscheck
F8BBCC utility 40.1 (10.2.93)
F8C588 ramlib 40.2 (5.3.93)
F8C9AC gameport 40.1 (8.3.93)
F8C9D6 keyboard 40.1 (8.3.93)
F8CA00 input 40.1 (8.3.93)
F8DFE0 mathffp 40.1 (16.3.93)
F8E482 con-handler 40.2 (12.5.93)
F90C40 console 40.2 (5.3.93)
F948C4 filesysres 40.1 (15.2.93)
F956F0 dos 40.3 (1.4.93)
F9E670 potgo 37.4 (28.1.91)
F9E7CE fs 40.1 (15.2.93)
FA4748 graphics 40.24 (18.5.93)
FBDBCC icon 40.1 (15.2.93)
FC0008 keymap 40.4 (12.3.93)
FC0C88 timer 39.4 (29.7.92)
FC1A74 misc 37.1 (8.1.91)
FC1B24 ramdrive 39.35 (21.5.92)
FC2118 disk 37.2 (21.4.91)
FC24CC ram 39.4 (9.8.92)
FC48D8 cia 39.1 (10.3.92)
FC4CC8 bonus 40.1 (15.2.93)
FC4DC8 expansion 40.2 (9.3.93)
FC4DE2 diag init
FC5950 shell 40.2 (4.3.93)
FC9DDC mathieeesingbas 40.4 (16.3.93)
FCAC7C romboot
FCAC96 strap 40.1 (8.3.93)
FCBB94 trackdisk 40.1 (12.3.93)
FCD8A0 battclock 39.3 (20.4.92)
FCE22C intuition 40.85 (5.5.93)
FE7BA8 gadtools 40.4 (24.5.93)
FED754 wb 40.5 (24.5.93)
FFEB44 battmem 39.2 (6.3.92)
Kickety-Split: 11114EF9 00F80002

[Dr. Dude]

i think i wil ritual burn the 40.70 roms

I tryed again, but this time whit just workbench 3.1 from the 3.5cd

fitted it to my 4000 whit the 40.70 roms....nothing...
i fitted back my old 3.0 roms. FLASH!... running...

busted 40.70 roms? Or is my A4000D just refusing to run A4000T roms

good thing new roms are on its way

[FOL]

Originally Posted by Dr. Dude

i think i wil ritual burn the 40.70 roms

I tryed again, but this time whit just workbench 3.1 from the 3.5cd

fitted it to my 4000 whit the 40.70 roms....nothing...
i fitted back my old 3.0 roms. FLASH!... running...

busted 40.70 roms? Or is my A4000D just refusing to run A4000T roms

good thing new roms are on its way

Sounds like you may have killed them (with static?), you have them in the right way round thankfully.

Its a shame you havent got it running, as I know it works.

[Dr. Dude]

Originally Posted by FOL

Sounds like you may have killed them (with static?), you have them in the right way round thankfully.

Its a shame you havent got it running, as I know it works.

not a chance, i have myself always grounded when working whit electronics.
And since this is Amiga i take extra care.
32euro down the drain...

[FOL]

Originally Posted by Dr. Dude

not a chance, i have myself always grounded when working whit electronics.
And since this is Amiga i take extra care.
32euro down the drain...

Hang on, you had them working. So it can only be inserting them incorrectly, shorting them out or static.

I think, the easiest solution would be connecting your hdd to a pc and seting it up through winuae. This way you can experiment without fear of damage to hardware.