+InsaneMultitasker #1 Posted January 10 This topic is intended for discussing development of the Geneve 9640 operating system (known historically as MDOS). Release history: Current development goals include: 1. Identify the most recent, stable source code files; recreate bug fixes as necessary 2. Integrate the TIPI development and the 6.70/7.00 development 3. Release an updated OS 4. Release the updated source code Updates: A long-standing barrier to releasing the next stable OS was a disk IO corruption bug that has recently been identified and (seemingly) corrected. (RESOLVED) 18 Jan 2021 - Combined 7.00 source base with TIPI support routines. SCSI Cache bug resolved. Organized/cleaned up source and MAKE file structures. Built OS using HRD4000B w/ram hardrive routines. v7.20 Current OS Memory Map: 8 1 Quote Share this post Link to post Share on other sites
+arcadeshopper #2 Posted January 10 Can you fix cd to be more predictable. I can probably get some examples today if needed.Sent from my LM-V600 using Tapatalk Quote Share this post Link to post Share on other sites
BeeryMiller #3 Posted January 10 What is not predictable? Quote Share this post Link to post Share on other sites
+InsaneMultitasker #4 Posted January 11 On 1/10/2021 at 8:33 AM, arcadeshopper said: Can you fix cd to be more predictable. I can probably get some examples today if needed. Yes, please. There are some limitations to CD and other commands due to available space in that segment of the OS. (16 bytes free!) We've removed DISKCOMPARE and DISKCOPY to free up some space in the command line interpreter, which might allow for some feature adds/corrections after a bit more analysis is completed. 4 Quote Share this post Link to post Share on other sites
+arcadeshopper #5 Posted Thursday at 06:27 PM Quote Share this post Link to post Share on other sites
mizapf #6 Posted Thursday at 06:58 PM It is predictable from what I see here. CD does not check whether the path exists; this has always been the case. Would be nice if it did, but takes more time. On the right, the trailing slash should be removed. The bad thing is that DIR requires the trailing slash. DIR MODULES will not deliver the contents DIR MODULES\ does it CD MODULES is OK CD MODULES\ will fail. Quote Share this post Link to post Share on other sites
BeeryMiller #7 Posted Thursday at 07:41 PM (edited) In the example on the left, you got the device error because you typed "module", not "modules" with the latter being the correct folder name. And sorta along the lines with what was posted above, the trailing slash was after the directory name was converted to a period so that "modules" became "modules." which that folder does not exist either. The CMD.exe window for Win10 allows one to: cd down\ to go to C:\>DOWN or cd down. to go to C:\>DOWN One route would require stripping a trailing "." or trailing "\" from the path request. Another option is to strip and error report and revert back to the original path if an invalid entry is made similar to what a MS-DOS prompt would do. This is worth documenting as an improvement "as time permits" as it would likely require changes in a number of places in the CLI code for consistency sake across a number of commands impacted. Edited Thursday at 07:42 PM by BeeryMiller Quote Share this post Link to post Share on other sites
+InsaneMultitasker #8 Posted 13 hours ago Happy Monday. MDOS 7.00 code base integrated with our TIPI work from the past month. Took the time yesterday to delete/organize the source folders. Compiled this morning using HRD4000B and ram hard drive support. Includes TIMODE2 alternative which frees up the dedicated MyWord ram (64k) for use. 5 Quote Share this post Link to post Share on other sites