Welcome, Guest. Please login or register.

Author Topic: OS 3.9 and Warm-Reboot  (Read 2030 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline MiAmigo

  • Arbiter of Succession
  • Sr. Member
  • ****
  • Join Date: Dec 2004
  • Posts: 391
  • Country: us
  • Thanked: 1 times
  • Gender: Male
    • Show all replies
Re: OS 3.9 and Warm-Reboot
« on: January 19, 2005, 05:01:22 PM »
Quote


The A2000 won't Cold Boot on cold start. I have to do
a CTRL-Amiga-Amiga to boot. This has something to do with
the GVP TekMagic accellerator script remapping KickStart.
I don't know how to fix this either.

Anyone know how to fix this .........????


I had this problem twice, under two different situations.

1). Whenever I try to cold boot my A2000 with my external SCSI CD already on. It always hangs, and I have to do a warm reboot.

2). I installed an application called 'HappyENV' which (this from the Aminet description)

"...is a kind of RAM disk handler specialized for environment variables
that are usually found in RAM:ENV. Because environment variables
(short: ENV vars) are usually quite small and there are lots of them,
HappyENV is optimized for lots of small files. This brings you the
following advantages:

* Smaller memory usage
* Faster accessing of ENV vars
* You can do "delete RAM:#? all" without hurting ENV vars
* Conceptionally much cleaner than the RAM: concept

This works by providing you an AmigaDOS(TM) handler for a ENV: device.

And there is an additional feature:
Every time a ENV var is accessed and cannot be found in ENV:, HappyENV
tries to copy it automatically from ENVARC:. This makes it possible to
leave out copying the whole ENVARC: directory to ENV: during boottime.
To avoid many disk accesses HappyENV remembers files that are not in
ENVARC:. So the additional advantages are:

* Faster booting
* Even smaller memory usage
* You do not have to clean up ENVARC:, because unused files in it will
  not be copied to ENV:

HappyENV should run on every Amiga(TM)."

I also installed StartupManager which (again, from Aminet)

"...replaces workbench's job of loading the programs in the
   SYS:WBStartup drawer. Instead StartupManager is the only program in this
   drawer and it will then load the pograms from another drawer or drawers
   as configured. A graphical display of programs being loaded is shown at
   the bottom of the workbench screen in a small window. StartupManager
   can be disabled by pressing the shift key while it is loading, this will
   stop all the programs in the Startup directory from being loaded.

Anyway, when I did the remap of kickstart to the ram of my GVP controller, I had the exact problem you describe with your A2000. The only way I could fix it was boot with a floppy, remove all the apps from the StartupManager folder, put them back into WBStartup, turn off the GVP remapping mode
from the CLI, and finally, remove the line that does it from s:startup-sequence. After that, I was okay, and was able to go back to using my third-party StartupManager.