Welcome, Guest. Please login or register.
Amiga Kit Amiga Store Iridium Banner AMIStore App Store A1200/A600 4xIDE Interface

Recent Posts

Pages: 1 ... 8 9 [10]
91
Amiga Hardware Issues and discussion / Re: OS3.2 Roms Installation
« Last post by Castellen on July 18, 2021, 04:06:40 AM »
I tried a quick sanity check using Blizkick to run the OS3.2 ROM image in a A3000D with CSmk2 060, it works fine.  Can't see any reason why the physical ROMs wouldn't work unless there was a problem with how they were written, or the two ROMs are exchanged.  The word-swapped EPROM binaries on the OS3.2 CD appear to be slightly mis-named, but the contents is correct otherwise.  i.e. if you recombine them and swap words, the resulting binary is the same as the A3000 ROM.

There's no harm in exchanging U180/U181 as there's a reasonable chance your physical ROMs have been mis-labeled.  So do give that a try, take care that pin 1 of the ROM matches that of the socket.

Shouldn't make any difference if the EPROMs are in a A3000T or A3000D.  The same ROMs should work in the A3000D, but you'll have to install them into the tower (adapter) PCB.

Unfortunately there's no easy way to tell if the ROMs have been written incorrectly without access to an EPROM programmer to check the contents of them.

A quick sanity check you can do is repeatedly press the caps lock key.  If the LED sticks (usually on) after 10 or so presses, it means the system isn't running at all; i.e. it's not reading in the keyboard serial data.  If the LED does turn on and off reliably, then the system is running (ROMs are working); though it's potentially waiting forever for scsi.device for some reason, or something else.

If you get stuck caps lock LED with the OS3.2 ROMs installed as you'd expect, or with U180/U181 positions exchanged, then there's most likely an issue with the data programmed into the EPROMs, in which case you'll need to return them.

In case you get stuck with the ROMs, send me a private message and I can put you in contact with someone local to you who can check the EPROM contents.
92
Amiga OS -- Development / Re: Amiga OS 3.2 released
« Last post by TribbleSmasher on July 17, 2021, 09:08:21 PM »
Quote
There is still an Expansion drawer, what is this for?
The same thing it has always been for?
There are still expansions initialising their drivers this way and OS3.2 is still supporting this and those expansions still work??
Really?
The only thing i've ever had in there was 'BuddhaSpeed', which is obsolete for, like, 10 years?
Quote
Workbenchs stack size is still 4kB?
Can be changed in WB prefs.
Yeah, but as 3.2 requires more resources anyway, why not set this to e.g. 16kB default?
93
Amiga Hardware Issues and discussion / Re: GVP RAM32 board with A2000-030
« Last post by marmotta on July 17, 2021, 02:41:00 PM »
@thebajaguy

Can be the rom?

At 50mhz the 1mb simm always do a defective on boot diagnostics, probably the a3001 at 50mhz not support 1mb simm, and can’t map memory on zorro2 space. With 4mb simm mapped high, the memory board (and the memory) is not visible, I can assume the card is not mapped on zorro2 space and based on your explanation the rom enable the ram and map it high… but this not happens! My Rom is 3.3 and insert it, or removing, nothing change.

The two roms u24 u25 are needed only for unix? In my board are missing.
94
Amiga Hardware Issues and discussion / Re: OS3.2 Roms Installation
« Last post by Tumbleweed on July 17, 2021, 01:12:42 PM »
Tried pretty much all the same things as the guy in the vid. Im almost certain the ROMs I have are the issue. Machine boots and works perfectly with 3.1 ROMS installed.

Last thing to try is is to install the 3.2 ROMs in my A3000D but I'm not yet sure they are comaptible as the 3000D has the ROM tower and doesnt have the ROM sockets on the main board.

Using OS3.2 with 3.1 ROMs seems to work ok. The main reason for upgrading from 3.1 to 3.2 was for the upgraded scsi as I am running the A3000T from a SCSI2SD card. I know you can get access to larger SD cards using a software solution using pacthes but I was aiming for a hardware solution with the latest scsi.device in ROM.

I do have an alternative solution and that is to put the 3.2 kickstart on my deneb and run it from there.

But that kinda defeats the purpose of buying the 3.2 ROMs. I could just have got the OS3.2 CD without the 3.2 ROM.

Any one else upgraded a A3000D/T with 3.2 ROMS? What's your experience been? And where did you but your ROMs?

Weed
95
Amiga Hardware Issues and discussion / Re: OS3.2 Roms Installation
« Last post by TribbleSmasher on July 17, 2021, 09:50:44 AM »
How do you test after swapping the ROMs?
If there is no floppy attached and no harddrive, you'll get a black screen too.
96
Amiga Hardware Issues and discussion / Re: OS3.2 Roms Installation
« Last post by Tumbleweed on July 17, 2021, 08:51:30 AM »
Read the FAQ. Seems the issue is with how the ROMS are labelled on the CD. The LO ROM lfor the A3000 looks to be incorrectly labelled. See vid here:

https://www.youtube.com/watch?v=u3R-7rJh9FE&t=13s

I think it only affects the A3000 ROMS haven't seen reports of other models havimg the same issue.

I'll be returning my ROMs for a new set.

Weed
97
Amiga Hardware Issues and discussion / Re: OS3.2 Roms Installation
« Last post by lionstorm on July 16, 2021, 09:32:03 PM »
98
Amiga Hardware Issues and discussion / Re: GVP RAM32 board with A2000-030
« Last post by marmotta on July 16, 2021, 09:23:10 PM »
Ok! But the question is: my ram32 board is damaged or it born to run at 33mhz and can’t go at 50mhz?

Sorry for my poor English :-)
99
General chat about Amiga topics / Re: Amiga onsite support in MA
« Last post by thebajaguy on July 16, 2021, 09:08:41 PM »
pm sent.
100
Amiga Hardware Issues and discussion / Re: GVP RAM32 board with A2000-030
« Last post by thebajaguy on July 16, 2021, 09:03:21 PM »
It can be said that a 50MHz-configured board will run at 33MHz or slower, but it's memory-access timing is not optimal for that clock.

The programmable logic in the PALs, combined with the jumpers (which control clock and bus-signal sources, some being negated, etc, if I am recalling correctly) produce the optimum timing for the board speed it was set up for.  Trying to go faster (clock) on a slower-configured memory board won't work.

Although some logic is common between boards for a few things (the memory-detect and/or AutoConfig details), there were no 'generic' part sets that applied to the address-generation/data-access logic.  It was timed to a clock speed for best performance.
Pages: 1 ... 8 9 [10]