+9640News Posted May 12 Author Share Posted May 12 This message has been edited. It looks like I overlooked one page, and it is unlikely 7.40 will work with a stock Geneve. There is something else I double checked in this release. Users that have been stuck on version 2.50 because they had not added the additional 32K upgrade, I am about 99% sure you can upgrade and use MDOS 7.40 in this release. There was a limitation when SCSI code was added to use zero wait state RAM for SCSI I/O after Version 2.50 up through version 7.30. 1 1 Quote Link to comment Share on other sites More sharing options...
+Schmitzi Posted May 12 Share Posted May 12 3 hours ago, InsaneMultitasker said: If you would like to walk through the upgrade process together, we could schedule a time to do so later this year. The programs run from the MDOS command line. the steps are simple so long as you prepare the files. yeah thanks, this sounds very good 🥰 "later this year" also sounds good So I have some more time for preparation and to read about, as I want to understand how it works. 2 Quote Link to comment Share on other sites More sharing options...
+dhe Posted May 12 Share Posted May 12 Thanks for uploading the gpl and geneve os source to github. are the load-tip and system-sys code 'paired'? 1 Quote Link to comment Share on other sites More sharing options...
+9640News Posted May 13 Author Share Posted May 13 All the LOAD-xxx files are paired to load AUTOEXEC from the same device SYSTEM-SYS was loaded from, assuming you are using the 2.00 eprom. Those LOAD-xxx files leaves two bytes in the on-chip ram of the 9995 to designate the device SYSTEM-SYS was loaded from. When the CLI "executes", it reads those two bytes to know how to auto-track the loading AUTOEXEC. 2 Quote Link to comment Share on other sites More sharing options...
+9640News Posted May 13 Author Share Posted May 13 It looks like I overlooked one of the two pages in 7.40. It does not appear 7.40 will work with a stock Geneve. Beery 1 Quote Link to comment Share on other sites More sharing options...
+InsaneMultitasker Posted May 14 Share Posted May 14 @9640News - tonight I realized / remembered that the PFM suite was updated in January 2022. Could you please incorporate the files into your release packet and/or add the ZIP to your first post? See the link to the post below. The core was updated to turn off all peripheral cards prior to initiating the standard DSR powerup scan, since a RESET cannot guarantee that all cards have been turned off. The same routine is also implemented in EXEC 2.7, upon return to the OS. The routine to turn off the cards has not been implemented (though maybe it should be!) in the MDOS XOP powerup sequence or GPL. I'll add that as an action item for review. My notes suggest I was planning to add the routine to the OS then simplify both EXEC and GPL. Anyway, I recommend reviewing your EPROM release for this code and if it is not present, consider adding it to a future release. 2 Quote Link to comment Share on other sites More sharing options...
+dhe Posted May 14 Share Posted May 14 Unless I missed it in the archive, I'd add Beery's new memtest - that would also be nice to have in github. 1 Quote Link to comment Share on other sites More sharing options...
+9640News Posted May 14 Author Share Posted May 14 18 hours ago, InsaneMultitasker said: @9640News - tonight I realized / remembered that the PFM suite was updated in January 2022. Could you please incorporate the files into your release packet and/or add the ZIP to your first post? See the link to the post below. The core was updated to turn off all peripheral cards prior to initiating the standard DSR powerup scan, since a RESET cannot guarantee that all cards have been turned off. The same routine is also implemented in EXEC 2.7, upon return to the OS. The routine to turn off the cards has not been implemented (though maybe it should be!) in the MDOS XOP powerup sequence or GPL. I'll add that as an action item for review. My notes suggest I was planning to add the routine to the OS then simplify both EXEC and GPL. Anyway, I recommend reviewing your EPROM release for this code and if it is not present, consider adding it to a future release. I have added to the original message both your PFM program and Dan's suggestion of MEMTEST. i had a small update on the MEMTEST program from things I was working on previously. I will look at adding MEMTEST source code to github. Beery 3 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.