Titanium anomoly

[atrax27407]

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???

[Asmusr]

Titanium it using some 'boot tracking' code that expects to find the CRU address of the last used DSR to at >83D0 and the ROM address of the device at >83D0.

[atrax27407]

Does the program possibly restrict drive designations to numeric drives (i.e., DSK1-DSK9)?

[Asmusr]

No, the only restriction as far as I can tell is that the device name must be 4 characters long.

[+InsaneMultitasker]

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.

[atrax27407]

Not the same physical RAMdisk. The HRD16 (DSK4-9) is at >1900 and the Horizon (DSKD-E) is at >1700. Both are using ROS832.

[atrax27407]

Sorry, the HRD16 is DSK4-DSKC.

[atrax27407]

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!!!

[+InsaneMultitasker]

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.

[Gazoo]

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

[atrax27407]

Gazoo,

 

You have no idea!!!!

[+OLD CS1]

Gazoo,

 

You have no idea!!!!

 

Like your avatar scaring the hell out of me every time I read one of your posts.

[atrax27407]

That is ATRAX spp. AKA "Funnelweb Spider". Tony McG and I were good friends in years past.