Welcome, Guest. Please login or register.

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

Description:

0 Members and 1 Guest are viewing this topic.

Offline melottTopic starter

  • Hero Member
  • *****
  • Join Date: Dec 2002
  • Posts: 989
    • Show only replies by melott
OS 3.9 and Warm-Reboot
« on: January 18, 2005, 06:28:00 PM »
Can anyone tell me what has to be done to get
my A3000 and A2000 to Warm-Reboot under OS 3.9 ??

The A3000 Cold Boots OS 3.9 fine but won't warm-reboot.
It has to be shut down and cold booted.

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.
Then if I want to do a Warm-Reboot it boots into the
OS 1.0 screen (I guess thats what the screen is).
The A3000 does the same, OS 1.0 screen............

Anyone know how to fix this .........????
Stealth ONE  8-)
 

Offline keropi

  • Hero Member
  • *****
  • Join Date: Sep 2004
  • Posts: 2466
    • Show only replies by keropi
Re: OS 3.9 and Warm-Reboot
« Reply #1 on: January 18, 2005, 08:45:07 PM »
that os3,9 warm reboot also troubles me, as it causes my picassoII to dissapear... I have to manually make a 2nd reboot in order for it to work... a fix should have been available for these probs!  :pissed:
 

Offline adolescent

  • Hero Member
  • *****
  • Join Date: Sep 2003
  • Posts: 3056
    • Show only replies by adolescent
Re: OS 3.9 and Warm-Reboot
« Reply #2 on: January 18, 2005, 09:40:12 PM »
Can you be more clear on the problem.  I don't know what an OS1.0 screen is.  Do you get an error message?
Time to move on.  Bye Amiga.org.  :(
 

Offline melottTopic starter

  • Hero Member
  • *****
  • Join Date: Dec 2002
  • Posts: 989
    • Show only replies by melott
Re: OS 3.9 and Warm-Reboot
« Reply #3 on: January 18, 2005, 10:48:29 PM »
Well ... I don't know if its really an OS 1.0 screen.
Its just a almost blank screen, says something like
'Amiga Dos' or something.

WorkBench doesn't load. Its like a CLI but commands
typed in don't execute.


Stealth ONE  8-)
 

Offline alphonsus

  • Full Member
  • ***
  • Join Date: Feb 2002
  • Posts: 166
    • Show only replies by alphonsus
Re: OS 3.9 and Warm-Reboot
« Reply #4 on: January 18, 2005, 11:49:56 PM »
> WorkBench doesn't load. Its like a CLI but commands
> typed in don't execute.

That sounds like a failure to find startup-sequence, possibly due to assigns not being in the correct place.

Try typing in a few of the default locations and see whether they exist - such as df0: and sys: (if they're missing you are in trouble!) but more importantly c: s: libs:

If the cli says they can't be found then the machine is failing to execute part of the rom that sets up those assigns at startup.

Having said that, if that is the case I don't know what to do about it, but at least it tells you a few things about what might be wrong.
Saw the light in 1990, found WinUAE in 2003
 

Offline melottTopic starter

  • Hero Member
  • *****
  • Join Date: Dec 2002
  • Posts: 989
    • Show only replies by melott
Re: OS 3.9 and Warm-Reboot
« Reply #5 on: January 19, 2005, 12:57:59 AM »

---------------
Try typing in a few of the default locations and see whether they exist - such as df0: and sys:
 (if they're missing you are in trouble!) but more importantly c: s: libs:
----------------

Nope... it doesn't reconize anything....

Its getting to be a pain ....(on the A2000)
I've playing around with Blitz (AmiBlitz) and in testing,
my stuff crashes alot :-D

Soooo I'd like to find the problem and fix it.
Stealth ONE  8-)
 

Offline Thomas

Re: OS 3.9 and Warm-Reboot
« Reply #6 on: January 19, 2005, 09:23:18 AM »

Getting to the AmigaDOS window means that you created a boot partition with the highest boot priority which does not have Workbench installed on it. Enter CD command to see which partition you are on and either use HDToolbox to change the bootpriority to be lower than your desired boot partition or install AmigaOS onto this partition.

If this only happens on a warm reboot, you probably have multiple hard drives and the one your boot partition is on does spin down upon reset and does not spin up again quick enough for AmigaOS to recognise it. Either swap the drives or move your boot partition to the remaining drive.

In general you should not mark a partition as bootable if you don't plan to install AmigaOS on it. In the worst case, if no boot partition remains, you get the insert-disk animation.

Bye,
Thomas

Offline MiAmigo

  • Arbiter of Succession
  • Sr. Member
  • ****
  • Join Date: Dec 2004
  • Posts: 391
  • Country: us
  • Thanked: 1 times
  • Gender: Male
    • Show only replies by MiAmigo
Re: OS 3.9 and Warm-Reboot
« Reply #7 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.
 

Offline Castellen

Re: OS 3.9 and Warm-Reboot
« Reply #8 on: January 19, 2005, 07:11:12 PM »
As Thomas suggested, check boot partitions and priorities are correct first.

I'd also suggest installing the two Boing Bag updates if you haven't already.  The ROM image updates fixed various problems people had with certain setup combinations, and more.

I have them here:
http://amiga.serveftp.net/downloads.html


To install, you need to boot from OS3.9 emergency disk and CD.  Then run the installer script from in the Boing Bag.
Install #1 first, then without rebooting you can install #2.

Boing Bag1 had a problem with the A4000T SCSI controller, causing failure to boot, they fixed it in #2.
There may be other similar things in #1 which may effect your setup, hence the reason for immediately installing #2.