Welcome, Guest. Please login or register.

Author Topic: Amiga One / OS4 problem  (Read 2347 times)

Description:

0 Members and 2 Guests are viewing this topic.

Offline IanoakleyTopic starter

Amiga One / OS4 problem
« on: February 04, 2006, 10:23:37 AM »
When I boot up my Amiga One I get the following message:

Guru Meditation : 80000003 Task 0X1ca35f ("voodoo") generated an error of type DSI on address 0X1420140.
Redzone was not damaged
Stack pointer is inside bounds.

You are then given option to kill/reboot/continue/GDB/Ignore/More

The only clue I get is that when I select more I get the message "please insert volume sdk in any drive. SDK:c/gdb:unknown command"

All very strange and of course I cannot boot into OS4.

All I can remember doing before this is install Wordworth 7.

Any OS4 / Amiga One guru experts out there who can assist me.
 

Offline xeron

  • Hero Member
  • *****
  • Join Date: Mar 2002
  • Posts: 2533
    • Show only replies by xeron
    • http://www.petergordon.org.uk
Re: Amiga One / OS4 problem
« Reply #1 on: February 04, 2006, 10:36:47 AM »
Is this the latest prerelease?

Do you mean that it worked before, then you installed wordworth and it stopped working?

Something is causing your Voodoo driver to crash, which is odd. Does Wordworth install anything in your startup-sequence, user-startup or WBStartup?

The error about gdb simply means you don't have the SDK installed, which isn't to do with the actual problem.

Edit: I notice you're a MAG member. Maybe someone from MAG could have a look at the problem in person? its always much easier to fix these things with the computer in front of you.
Playstation Network ID: xeron6
 

Offline motorollin

  • Hero Member
  • *****
  • Join Date: Nov 2005
  • Posts: 8669
    • Show only replies by motorollin
Re: Amiga One / OS4 problem
« Reply #2 on: February 04, 2006, 11:13:45 AM »
I don't know how to help you, but I'm glad OS4 still has gurus :-) Do they look the same as 3.x gurus with the flashing red box?

--
moto
Code: [Select]
10  IT\'S THE FINAL COUNTDOWN
20  FOR C = 1 TO 2
30     DA-NA-NAAAA-NAAAA DA-NA-NA-NA-NAAAA
40     DA-NA-NAAAA-NAAAA DA-NA-NA-NA-NA-NA-NAAAAA
50  NEXT C
60  NA-NA-NAAAA
70  NA-NA NA-NA-NA-NA-NAAAA NAAA-NAAAAAAAAAAA
80  GOTO 10
 

Offline PulsatingQuasar

  • Sr. Member
  • ****
  • Join Date: Mar 2003
  • Posts: 340
    • Show only replies by PulsatingQuasar
    • http://none
Re: Amiga One / OS4 problem
« Reply #3 on: February 04, 2006, 11:30:35 AM »
If you used the installer of WordWorth 7 then it has overwritten some files it shouldn't have!!

I had this too when I installed WordWorth 7. I get remember exactly anymore which files they were but I can remember it did it.

You have to put back the original OS 4 files.
BlizzardPPC powered!!
AmigaOne-XE G3 800 MHz, 512 MB RAM, Radeon 8500, OS4
 

Offline IanoakleyTopic starter

Re: Amiga One / OS4 problem
« Reply #4 on: February 04, 2006, 02:19:19 PM »
I'm pretty certain that was the case with Wordworth.

Unfortunately I do not have an OS4 CDROM (a very long saga !!) however OS4 is backed up on a HDD partition. Have you any advice how the files from the backup partition can be copied over the files on the OS4 partition.
 :-?  :-?
 

Offline justthatgood

  • Hero Member
  • *****
  • Join Date: Dec 2003
  • Posts: 579
  • Country: us
    • Show only replies by justthatgood
Re: Amiga One / OS4 problem
« Reply #5 on: February 04, 2006, 02:29:40 PM »
Quote


Ah yes.  This is exactly why I now keep all my Amiga and system software seperate from any of the other software in the house.  They are kept in a cd-jacket and a plastic 3.5 disk boxes in a nice dark dry closet.

Nobody touches those things anymore. Under penalty of death or severe yelling.
[color=008000]Pluto[/color]:Amiga4KD- 64040/16megs/1GB WD/PAR 2150/1942/WB3.0,3.1,3.9
[color=800080]Amanda[/color]:Amiga2KHD/A2620/8MegSupraRam2k/A2091/VLab
 

Offline Framiga

  • Hero Member
  • *****
  • Join Date: May 2003
  • Posts: 4096
    • Show only replies by Framiga
Re: Amiga One / OS4 problem
« Reply #6 on: February 04, 2006, 02:51:09 PM »
Take a look here

Same problem

EDIT- nope . . . it was starting WW7 :-(
 

Offline PulsatingQuasar

  • Sr. Member
  • ****
  • Join Date: Mar 2003
  • Posts: 340
    • Show only replies by PulsatingQuasar
    • http://none
Re: Amiga One / OS4 problem
« Reply #7 on: February 04, 2006, 03:38:57 PM »
I think your only shot is via holding the 2 mouse buttons and booting without startup-sequence then.

Do you not have login at Hyperion to download OS 4 updates? Isn't one of the updates an ISO?

I guess if WordWorth updated files that it shouldn't have, it will be in either C: or LIBS:. So maybe you can copy the contents from one folder to another in the DOS prompt then.

By the way: I created a second boot partition on my system called Workbench Backup with a lower boot priority. As soon as something happens to my main partition I go into the early startup sequence and disable the main partition so the backup partition then boots.
BlizzardPPC powered!!
AmigaOne-XE G3 800 MHz, 512 MB RAM, Radeon 8500, OS4
 

Offline IanoakleyTopic starter

Re: Amiga One / OS4 problem
« Reply #8 on: February 04, 2006, 10:28:35 PM »
Yes I have a log in and will investigate that option.I assume if that is the case everything can be uodated using rekaese 3 without using the original CD which I've not got.

There is also a similar boot arrangement on the HDD and as the drive is so large I also copied all the system files to that partition. Using that partition I bit the bullet and copied all the files overwriting DH0. The system appears to boot however one snag - I have a TFT screen and it then goes blank and 've just given away my CRT monitor!!. Any way you can change screen prefs so TFT can be used and I can then reset up OS4.

 

Offline Matt_H

Re: Amiga One / OS4 problem
« Reply #9 on: February 04, 2006, 10:57:24 PM »
Try booting with no startup-sequence from the Early Boot menu. That should be displayed in a default screenmode displayable by anything. Then rename SYS:Prefs/Env-Archive/Sys/screenmode.prefs to something else. You should boot into another default display mode. Then fire up P96Mode and rebuild your screenmodes.