#Minor A3000 Problems
9 messages in this thread
Chris,
As to the problems in deleting Txed.backup files I can't think of a thing
to help. I've been helping my dealer here set up his 3000, first Amiga
he's had with a hard drive! I've run into files that just won't delete on
the 3000 too!
Anyway I've tried the mouse buttons in every way possible because I was
TRYING to get to WB 1.3 so we could actually run something. At least I
learned here that you have to do a cold power up while holding both mouse
buttons down. That brings me to your problem on mounting partitions. I
never saw a screen that allowed you to mount or not mount a partition, it
doesn't exist on our machine. I can tell you how to get there though, I
hope.
In the System drawer there should be an icon named HDToolBox, double click
on that one and you'll get all the hard drive functions you could ever
want. Click on partition drive, you will then go to a graphic display of
the partitions available. If you change the sizes that will of course wipe
out the data on the partition. Click on the box Advanced Options, several
more selections will appear, one of them is a box marked "Change File
System for Partition" click on that box and you'll enter another screen.
In this screen you will see a box that selects "Automount this Partition",
you can choose Yes or No. Of course if you choose No you can't access the
partition once you've booted. It's just there. I've found no way to
manually mount a partition after booting. Anyway you click OK to exit that
screen, and OK to exit the next screen up, then you should be at the final
screen. On the bottom right is a box "Save Changes to Drive", click on
this to make your selections take effect.
The Mount/NoMount selection is about the only thing I can find that won't
corrupt the entire partition. That and the selection for making it a
bootable partition. Everything else seems to wipe the partition. Hope
this helps. It sure isn't as simple as what you were describing but I think
that this is what the final method will look like.
Keith
Thanks for the reply, Keith. I have a feeling the screen I'm talking about
went away with the latest version of the OS. It was nothing critical –
just a nice little feature. I mainly wanted to make sure my 3000 wasn't
going south on me!
— CJC —
Chris,
Somehow those nice little features sometimes do disappear! Hope your 3000
stays healthy, something my 2000 hasn't been doing much lately!
Keith
Chris,
I have the latest 'release' version of 2.0 on my 3000, and that screen
comes up when I hold down both mouse buttons during a warm boot.
-larry
Well, I guess it's back to the drawing board for me. When you say latest
release, I assume you mean beta 5? I'm pretty sure I tried both buttons
during a warm boot, but I'll experiment some more. I guess my next step is
reformatting the whole drive and reinstalling the OS. Boy, I hate doing
that.
Thanks for the info!
— CJC —
Chris,
Not sure which 'beta' it is. It's called the 'Release 2.0'.
Oh… forgot to mention. It only presents that screen when you warm boot
and hold down the mouse buttons from 2.0
-larry
I too have "the latest" 2.0 on my Amiga 3000 and it was delayed in shioment
er shipment to get it installed. To the best of my knowledge it is not
Beta 5 anymore.
HarryM
Harry,
My 2.0 (under Version on the WB menu) is 36.68. My local dealer is
on 36.10. What's is your version.
My dealers 3000 has more ram than mine when booted up. He has 1 meg
fast and I did as well. Seems like my version 2.0 took up more ram.
Thanks! Jamie
Jamie,
I have the same version you do. Kickstart is 36.141. The version
the dealers received (assuming one of the first machines) was still a beta
version. The version we have is supposed to be "final" but I doubt it will
be.
I don't know if you have dissassembeled your 3000, but I have and
found the current ROMS to be on a piggyback board that plugs into the ROM
sockets. Seems like Commodore can't get away from the "daughterboard"
concept.
I'll probably retain the 1.3 / 2.0 setup on the hard drive when the
new roms come out.
On a more interesting note, some people I have talked to say that
certain hardware doesn't work in the 3000 that does in the 2000. Could be
a simple matter of reserved bits in autoconfig now being used were set
wrong. I think the development push was more along the software for 2.0
than hardware for the 3000 and this is understandable. I believe that one
should test software and hardware on all platforms, not just assume it will
work.
Harry Manolopoulos