#A1000/Rejuvenator Probs
9 messages in this thread
Greg,
Hey, I just bought Denny Atkins' Rejuvenated Amiga 1000, But I am having
some problems with it. Hopefully you might be able to offer some insight
and answers as to what might be causing the problems and how to corrent
them.
First, when I received his computer I plugged it in with no peripherals
attached (except the monitor of course.) The screen went white, 2 shades of
grey, then the Guru visited…Oh…I had a workbench in the drive too.
Second, I took the workbench out and did a warm reboot. Nothing…the
screen just stayed white.
Third, I shut the machine off for 10 seconds and turned it back on with
no disk in the drive. The screen went white, then 2 shades of grey and
then it asked for a workbench. I shut the machine off to see if it would do
it again, but it did not. Instead it just kept cycling, white, grey, grey,
about five seconds, white, grey, grey….. It does not ask for workbench.
The machines works fine if I switch the switch and insert a Kickstart on
disk, but it won't boot up properly with the ROM.
My wife, on a whim, decided to try it herself after a few hours. She
turned it on and it actually asked for a workbench. She inserted the
workbench into the drive but the machine never accessed the drive. It just
hung.
This whole thing is real weird because Denny tested it with a 2.0 ROM and
it worked, and he booted it up with the 1.3 ROM right before he shipped it
to me. When I got it, now it doesn't work.
Any help would be greatly appreciated. I'm using it right now with the
disk-based kickstart, but I need to have it with the ROM working,
especially when 2.0 comes out.
Thank you for any reply.
…1200 N81N ……………………. … …-….1200 N81N
My best feelings are that the ROM is misinserted or the socket is warped
due to handling. The molex near the PALs are another good area to look for
poor contact. It is very unusual to have the ROM not work; especially when
the usual failure is that the ROM does work and the disk mode fails. You
might also check to make sure that all the pins in the Rejuvenator (the
machine pins) are firmly and evenly in their sockets in the motherboard;
they might have gotten loose in transport.
Denny had reported a 2.0 problem that no one else can repeat, and I
suspected a bad molex connection for the one of the upper address lines at
I could not repeat the problem.
-Greg
I'm curious as to what problem Denny encountered in 2.0. I've noticed
something curious since I started using 2.0 exclusively lately. Every once
in awhile while reading or writing to the Quantum Hard drive, it will
freeze up with the drive late staying on and no further hard drive access
until I reboot the computer. Now this usually happens during the read or
write operation, and of course if during the write usually requires the
Hard drive to be revalidated. Now this never happened before while I was
using 1.3, and didn't start until I switched over to 2.0. I'm using 2.03 on
the 3000. Any known bugs in the 2.03 release that could cause this? I still
need to go through my startup-sequence and comment out a line at a time to
see if something running in the background is messing things up, but since
it's so random, it will take awhile. But I can increase the chances of
lockup if I do some heavy disk operations, like reading or writing 24bit
pictures for the Ham-E 8(
John
It was related to autoconfiguring problems when he upgraded his 8 up in
memory. Seemed to cause Ados to think there was a meg of C00000H ram, which
is impossible with the Rejuvenator. No one is able to duplicate this
problem, but no one has his configuration: A1000, 2.0, ADSpeed, Toolbox,
Rejuv, 8 up, and hard disk controller.
As far as 2.0 goes, I haven't looked at 2.03 since December. It has changed
considerably since then. 2.04 was what Denny was having trouble with, but I
don't care to elaborate further, although we developers have been told 2.04
is no longer subject to our non-disclosure agreement.
-Greg
– via Whap!
Greg, just a guess, but I believe the ICD products (at least some of
thier memory cards) configure themselves in funny places. You might lok at
the ADSpeed and see if that is causing any conflicts.
Keith
Well, teh problem showed up after Denny added memory to his ZorroII 8-UP.
Prior to that everything was OK, So I doubt that the ADSpeed changed
anything.
-Greg
Thanks for the reply.
Strangely, the machine suddenly started working right. One day it
didn't, the next day it did. It's been running for at least 2 days now
without any problems. Don't know what the prob was, hope it doesn't come
back.
Now I've got another problem, but I think I can attribute it to the fact
that I haven't got the terminating resistors I need for my SCSI drive. I
format it and it shows no error and then I start getting read/write error
after read/write error. Looked at the used 100 meg drive I just bought and
saw that it didn't have the terminating resistors. That might be the
problem (at least I hope it is as easy as that.)
Thanks again for the reply and please let me know a few things.
1. When will I be seeing the 2 meg Agnus for the Rejuvey? 2. Will it
take some kind of RAM expansion on the Rejuvey?
3. How can I make the 4 meg SIMM upgrade mentioned in the Docs?
4. How much will the 2 meg Agnus thingie cost? Thanks
again….laterz…
The 2 Megs Agnus/Chip Ramupgrade has been available for 2 months. I don't
know what Expert is charging, call (606) 371-9690. You might want to update
the registration with them so they'll have you in their database and you
get newsnotes sent occationally. Is is replacemnet chips on teh
Rejuvenator. I've describeed the process here on CIS twice in the last two
weeks, it should still be here somewhere.
There is no SIMM upgrade that fits on the Rejuveantor. Please reread the
manual.
-Greg
Sounds like either the Rejuvinator daughter board or one of the chips, or a
combination is creeping out of the sockets. If you have any reasonble tech
skills, ground yourself with a static strap (better safe than sorry) and
gently reseat all the connectors and chips by applying gentle but firm
pressure on them.
This is a common problem with new computers after awhile, and especially
with computers that have gone through shipping.