Jump to content
IGNORED

Titanium anomoly


atrax27407

Recommended Posts

I decided to install TITANIUM on one of my RAMdisks and have run into a peculiar problem. It runs fine when installed on my HRD16 in DSK9. I simply run the program file TITA and everything works great, However, when I install the files on my Horizon on DSKD and use exactly the same procedure, I get a "File Error 7" message. Rasmus???

Link to comment
Share on other sites

I decided to install TITANIUM on one of my RAMdisks and have run into a peculiar problem. It runs fine when installed on my HRD16 in DSK9. I simply run the program file TITA and everything works great, However, when I install the files on my Horizon on DSKD and use exactly the same procedure, I get a "File Error 7" message. Rasmus???

Is DSKD on the same physical RAMdisk as DSK9? If not, what are the differences i.e. ROS, CRU, etc.
Link to comment
Share on other sites

With Tim Tesch's help, I solved the Titanium problem. I found out that it would run from DSKB as well as DSK9. After a bit of poking around in the code, I changed "DSK1" in the TITA program to "DSKD" and it runs very nicely from DSKD now. I still don't have any idea what the problem might be but I have a working copy on my RAMdisk!!!

Link to comment
Share on other sites

At the very least we were able to confirm Titanium and the ROS are working together to load the files from DSKD.

 

What doesn't make sense is that your DSKD sector edit should have been overwritten in memory by the boot tracking (based on what I see in the startup routine). I suppose if the generic "DSK" was nabbed, this could explain the failure but then I would expect Titanium to look on DSK1. for the files, since the "1" would not have been overwritten.

 

Perhaps there are differences between the Titanium90 disk image I looked at and the version you are using. Most peculiar.

Link to comment
Share on other sites

At the very least we were able to confirm Titanium and the ROS are working together to load the files from DSKD.

 

What doesn't make sense is that your DSKD sector edit should have been overwritten in memory by the boot tracking (based on what I see in the startup routine). I suppose if the generic "DSK" was nabbed, this could explain the failure but then I would expect Titanium to look on DSK1. for the files, since the "1" would not have been overwritten.

 

Perhaps there are differences between the Titanium90 disk image I looked at and the version you are using. Most peculiar.

 

Lots of peculiar stuff happening recently. ;)

 

Gazoo

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...