Welcome, Guest. Please login or register.

Author Topic: Timberwolf: os4depot vs aminet Grim Reaper DSI (Data Storage Interrupt)  (Read 3957 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline yssing

  • Hero Member
  • *****
  • Join Date: Apr 2002
  • Posts: 1521
    • Show only replies by yssing
    • http://www.yssing.org
Re: Timberwolf: os4depot vs aminet Grim Reaper DSI (Data Storage Interrupt)
« Reply #14 from previous page: January 24, 2018, 09:01:56 PM »
Those darned DSI errors. They are the main reason, why i haven't switched completely to AOS4
 

Offline AC/DC HACKER!

  • Newbie
  • *
  • Join Date: May 2017
  • Posts: 4
    • Show only replies by AC/DC HACKER!
Re: Timberwolf: os4depot vs aminet Grim Reaper DSI (Data Storage Interrupt)
« Reply #15 on: January 24, 2018, 10:16:34 PM »
Hello,

 I was attempting to get Timberwolf to run on my X5000 also, but it doesn't function too well outside of a partition formatted with FFS from Amiga OS 4.x's FFS.  Yes, it DOES function that way.  I've done a lot of testing.  However, Odyssey is a very good replacement but I still (even at the start of 2018) would love to use Timblerwolf.  I'm a huge fan of Firefox (except the new Quantum edition....very ugly).

 If you wish to persist with Timberwolf, make a small partition formatted with FFS Standard or it will crash often OS 4.x.


Spectre660: Appreciate the files archive, I shall check that.  I didn't know about that until I saw your post.

Quote from: cehofer;835170
I was trying to get Timberwolf so I downloaded it from os4depot.  I performed all the tasks in the timberwolf doc but everytime I would start Timberwolf, it would grim reaper.  So I gave up on it.

I was looking at what exactly a Grim Reaper "Type of crash: DSI (Data Storage Interrupt) exception" is.  Since I wrote another post about how my XE kept freezing until I installed a new Barracuda Hard Drive, I was wanting to know if it was related.  I came across this post.

http://forum.hyperion-entertainment.biz/viewtopic.php?f=14&t=3031&p=33923&hilit=timberwolf+grim+reaper#p33923

This is from 2015 where a user found that the os4depot Timberwolf archive is the current version of 4.0.1.0252 but all the folders are missing.  The Aminet Timberwolf archive is complete but version 4.0.1.182.  So I did as the user of this post did and downloaded the Aminet version and it worked.  I also followed his lead and copied all the folders from the Aminet version into the OS4depot version and now that one works.

Can somebody fix the os4depot Timberwolf archive so it is complete and works?  Aminet needs to be updated with the current version as well.

Also can anybody tell me what a Grim Reaper "Type of crash: DSI (Data Storage Interrupt) is?  When the man with the sickle appears it is always of this type.
 

Offline AC/DC HACKER!

  • Newbie
  • *
  • Join Date: May 2017
  • Posts: 4
    • Show only replies by AC/DC HACKER!
Re: Timberwolf: os4depot vs aminet Grim Reaper DSI (Data Storage Interrupt)
« Reply #16 on: January 27, 2018, 06:07:17 PM »
Update: I was using Timberwolf with an older archive.  I  also noticed that making a couple changes improved performance.  I got  the ~newer~ version of Timberwolf and added the files from the LZX  archive (read above).  From Tools/Options changing "When Timberwolf starts:" to "Show  my windows and tabs from last time" helps a lot.  This also makes  "about:config"'s "browser.showQuitWarning" not needed, so keeping it at  false.  If this is made to true then Timberwolf causes or crashes when  you exit it after you're prompted to Save tabs.  I've now been able to  run it from whatever partition and filesystem.

 However, it does have a  memory leak (2MB...??).  If you exit and start it often you'll notice  it.  It also becomes slower and causes X5000 to hang a bit if you use  more than 5 to 7+ tabs, as I do with Firefox...I have more than 10  usually.  Same with WinUAE 3.6.0, of course.
 So, it's a cool browser with this understanding but it's  not as powerful as Odyssey...but has great potential if it were to be  developed.  It loads a little faster than Odyssey (not a problem to me,  just observation).  But a big point...it won't play YouTube videos or  videos from other sites like Odyssey does.  Anyone getting into  or wanting to use Timberwolf, it's still a very good general browser.   I'm glad to know that it does indeed function on SFS02 as I previously  thought it does not; and only on FFS.
 A side note, from  "about:config" ...if you filter with "Firefox" and change  "general.useragent.compatMode.firefox" to true then you won't get  warnings about the browser being outdated as much, or sites informing  you your browser isn't supported.  :-)  I'm sure there are other tips I haven't discovered..and maybe there's a Flash/Shockwave plugin or Library I haven't discovered yet..anyway, cool Browser.  I hope this is helpful to others.
 

Offline magnetic

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2531
    • Show only replies by magnetic
Re: Timberwolf: os4depot vs aminet Grim Reaper DSI (Data Storage Interrupt)
« Reply #17 on: January 28, 2018, 01:29:30 AM »
Timberwolf has been crap and broken since its release...
bPlan Pegasos2 G4@1ghz
Quad Boot:Reg. MorphOS | OS4.1 U4 |Ubuntu GNU-Linux | MacOS X

Amiga 2000 Rom Switcher w/ 3.1 + 1.3 | HardFrame SCSI | CBM Ram board| A Squared LIVE! 2000 | Vlab Motion | Firecracker 24 gfx

Commodore CDTV: 68010 | ECS | 9mb Ram | SCSI -TV | 3.9 Rom | Developer EPROMs
 

Offline ferrellsl

Re: Timberwolf: os4depot vs aminet Grim Reaper DSI (Data Storage Interrupt)
« Reply #18 on: January 28, 2018, 05:49:48 PM »
Quote from: magnetic;835501
Timberwolf has been crap and broken since its release...



I agree and the Friedens were supposed to release the source code once the port was completed but they sat on it for 2 years or more before releasing only portions of the code which were broken and wouldn't build.  That's 2 years that community programmers could have used to comb thru the code and update/upgrade/fix bugs, but apparently that wasn't one of their priorities.  

To this day, I don't think anyone has been able to get it to build with what the Friendens released.
 

Offline magnetic

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2531
    • Show only replies by magnetic
Re: Timberwolf: os4depot vs aminet Grim Reaper DSI (Data Storage Interrupt)
« Reply #19 on: January 29, 2018, 01:39:03 AM »
Quote from: ferrellsl;835515
I agree and the Friedens were supposed to release the source code once the port was completed but they sat on it for 2 years or more before releasing only portions of the code which were broken and wouldn't build.  That's 2 years that community programmers could have used to comb thru the code and update/upgrade/fix bugs, but apparently that wasn't one of their priorities.  

To this day, I don't think anyone has been able to get it to build with what the Friendens released.


How many thousands of dollars did they take from us for that?
bPlan Pegasos2 G4@1ghz
Quad Boot:Reg. MorphOS | OS4.1 U4 |Ubuntu GNU-Linux | MacOS X

Amiga 2000 Rom Switcher w/ 3.1 + 1.3 | HardFrame SCSI | CBM Ram board| A Squared LIVE! 2000 | Vlab Motion | Firecracker 24 gfx

Commodore CDTV: 68010 | ECS | 9mb Ram | SCSI -TV | 3.9 Rom | Developer EPROMs
 

Offline ferrellsl

Re: Timberwolf: os4depot vs aminet Grim Reaper DSI (Data Storage Interrupt)
« Reply #20 on: January 29, 2018, 02:49:41 AM »
Quote from: magnetic;835537
How many thousands of dollars did they take from us for that?



If my memory serves me correctly it was around $4000, but I could be wrong....it's been quite a while .
 

Offline broadblues

Re: Timberwolf: os4depot vs aminet Grim Reaper DSI (Data Storage Interrupt)
« Reply #21 on: January 29, 2018, 08:49:52 AM »
Quote from: Acill;835207


As far as DSI errors it has something to do with the disks being to fast or something I hear for the OS. You can ignore it. A lot of people get them in things other than Timberwolf. Its popped up for me a few times on my X5000 too. Much more since getting a SSD on it.


A DSI has nothing at all to do with the disk speed.

It stands for Data Storage Interupt and means a program has attampted to read from or write to a protected or non existant memory address.

The reason is different for every program, though attempts to read from NULL are perhaps most common.

The consequences are different for every program, depending on how they triggered the error, sometimes you can safely ignore them, somethimes not.

If you get more with a faster drive then likely the prgram that's throwing them has a race condition shown up by faster resposonses, send abug report to the author!