http://www.ninerpedia.org/api.php?action=feedcontributions&user=Jedimatt42&feedformat=atomNinerpedia - User contributions [en]2024-03-29T15:17:10ZUser contributionsMediaWiki 1.37.1http://www.ninerpedia.org/index.php?title=Disk_directory_reader_in_BASIC&diff=50333Disk directory reader in BASIC2020-07-26T18:56:53Z<p>Jedimatt42: </p>
<hr />
<div>Catalog file access from Basic - this relates to disks formatted with the original TI hardware and software:<br />
<br />
See also: [[TI Disk format]]<br />
<br />
The Catalog file can be accessed as a read-only file by the Basic user. The file has no name, and is of the INTERNAL, FIXED format type.<br />
<br />
The file can be opened by (for example):<br />
OPEN #l:"DSK.",lNPUT,INTERNAL,RELATlVE<br />
The record length will automatically be defaulted by Basic to the correct value, so this should not be entered. If however the user wants to specify the length, then it must be specified as 38 - all other lengths will result in an error message.<br />
<br />
The Catalog file acts as if it is Protected, and as mentioned above, it will only allow INPUT access.<br />
<br />
The file is written in the normal Basic INTERNAL format, and each record contains four items: one string and three numerics. There are 128 records in the file, and they are numbered 0 thru 127.<br />
<br />
Record 0:<br />
This record contains data about the volume for which the catalog file was created. The string gives the name of the disc (up to 10 characters) and the numerical items are as follows:<br />
1. Always 0 (for record 0)<br />
2. Total number of sectors on the disc <br />
3. Total number of free sectors on the disc <br />
<br />
Records 1 thru 127:<br />
These records contain information on the corresponding file in the Catalog. Non existant files will give a null string for the first item, and 0’s (zeros) for the numeric items. Files which exist will give the file name for the string, and the following numeric items:<br />
1. = Filetype (if number is negative, file is protected)<br />
1= DISPLAY/FIXED datafile<br />
2= DISPLAY/VARIABLE datafile<br />
3= INTERNAL/FIXED datafile<br />
4= INTERNAL/VARIABLE datafile<br />
5= Memory Image file (Program File) <br />
6= Directory (Extension for devices that support them)<br />
2. = Number of AUs allocated to the file<br />
3. = Number of bytes per record (0 for type 5 file)<br />
<br />
<br />
<br />
This TI BASIC program reads the directory of a disk and prints it on the screen. The P flag indicates protection. <br />
<br />
100 CALL CLEAR<br />
110 DIM TYP$(5)<br />
120 TYP$(1)="DIS/FIX"<br />
130 TYP$(2)="DIS/VAR"<br />
140 TYP$(3)="INT/FIX"<br />
150 TYP$(4)="INT/VAR"<br />
160 TYP$(5)="PROGRAM"<br />
170 INPUT "MASTER DISK(1-3)?":A<br />
180 A=INT(A)<br />
190 IF A<1 THEN 170<br />
200 IF A>3 THEN 170<br />
210 OPEN #1:"DSK"&STR$(A)&".",INPUT,RELATIVE,INTERNAL<br />
220 INPUT #1:A$,J,J,K<br />
230 PRINT "DSK";STR$(A);" -DISK NAME= ";A$:"FREE= ";K;"USED= ";J-K<br />
240 PRINT:"FILE NAME SIZE TYPE P":"__________ ______ ________ _"<br />
250 FOR LOOP=1 TO 127<br />
260 INPUT #1:A$,A,J,K<br />
270 IF LEN(A$)=0 THEN 350<br />
280 PRINT:A$;TAB(12);J;TAB(19);TYP$(ABS(A));<br />
290 IF ABS(A)=5 THEN 320<br />
300 B$=" "&STR$(K)<br />
310 PRINT SEG$(B$,LEN(B$)-2,3);<br />
320 IF A>0 THEN 340<br />
330 PRINT TAB(28);"P";<br />
340 NEXT LOOP<br />
350 CLOSE #1<br />
<br />
You can easily expand this program to consider subdirectories; just replace the number input in line 170-200 by a direct string input and open the given path name in line 210. <br />
<br />
Also, directories can be identified in the listing by extending the set of types. Type 6 represents a directory. Line 110 expands the array, 161 adds the mapping of type 6 to the label to print. Line 290 must be altered to skip printing the record length as was done for PROGRAM type files.<br />
<br />
100 CALL CLEAR<br />
110 DIM TYP$(6)<br />
120 TYP$(1)="DIS/FIX"<br />
130 TYP$(2)="DIS/VAR"<br />
140 TYP$(3)="INT/FIX"<br />
150 TYP$(4)="INT/VAR"<br />
160 TYP$(5)="PROGRAM"<br />
161 TYP$(6)="DIR "<br />
170 INPUT "DEVICE?":D$<br />
210 OPEN #1:D$&".",INPUT,RELATIVE,INTERNAL<br />
220 INPUT #1:A$,J,J,K<br />
230 PRINT D$;" -VOL=";A$:"FREE=";K;"USED=";J-K<br />
240 PRINT:"FILE NAME SIZE TYPE P":"__________ ____ __________ _"<br />
250 FOR LOOP=1 TO 127<br />
260 INPUT #1:A$,A,J,K<br />
270 IF LEN(A$)=0 THEN 350<br />
280 PRINT:A$;TAB(12);J;TAB(17);TYP$(ABS(A));<br />
290 IF ABS(A)>=5 THEN 320<br />
300 B$=" "&STR$(K)<br />
310 PRINT SEG$(B$,LEN(B$)-2,3);<br />
320 IF A>0 THEN 340<br />
330 PRINT TAB(28);"P";<br />
340 NEXT LOOP<br />
350 CLOSE #1<br />
<br />
[[Category:Programming]]</div>Jedimatt42http://www.ninerpedia.org/index.php?title=Disk_directory_reader_in_BASIC&diff=50332Disk directory reader in BASIC2020-07-26T18:19:10Z<p>Jedimatt42: Add concrete example of expanding BASIC catalog for devices that support directories.</p>
<hr />
<div>Catalog file access from Basic - this relates to disks formatted with the original TI hardware and software:<br />
<br />
See also: [[TI Disk format]]<br />
<br />
The Catalog file can be accessed as a read-only file by the Basic user. The file has no name, and is of the INTERNAL, FIXED format type.<br />
<br />
The file can be opened by (for example):<br />
OPEN #l:"DSK.",lNPUT,INTERNAL,RELATlVE<br />
The record length will automatically be defaulted by Basic to the correct value, so this should not be entered. If however the user wants to specify the length, then it must be specified as 38 - all other lengths will result in an error message.<br />
<br />
The Catalog file acts as if it is Protected, and as mentioned above, it will only allow INPUT access.<br />
<br />
The file is written in the normal Basic INTERNAL format, and each record contains four items: one string and three numerics. There are 128 records in the file, and they are numbered 0 thru 127.<br />
<br />
Record 0:<br />
This record contains data about the volume for which the catalog file was created. The string gives the name of the disc (up to 10 characters) and the numerical items are as follows:<br />
1. Always 0 (for record 0)<br />
2. Total number of sectors on the disc <br />
3. Total number of free sectors on the disc <br />
<br />
Records 1 thru 127:<br />
These records contain information on the corresponding file in the Catalog. Non existant files will give a null string for the first item, and 0’s (zeros) for the numeric items. Files which exist will give the file name for the string, and the following numeric items:<br />
1. = Filetype (if number is negative, file is protected)<br />
1= DISPLAY/FIXED datafile<br />
2= DISPLAY/VARIABLE datafile<br />
3= INTERNAL/FIXED datafile<br />
4= INTERNAL/VARIABLE datafile<br />
5= Memory Image file (Program File) <br />
2. = Number of AUs allocated to the file<br />
3. = Number of bytes per record (0 for type 5 file)<br />
<br />
<br />
<br />
This TI BASIC program reads the directory of a disk and prints it on the screen. The P flag indicates protection. <br />
<br />
100 CALL CLEAR<br />
110 DIM TYP$(5)<br />
120 TYP$(1)="DIS/FIX"<br />
130 TYP$(2)="DIS/VAR"<br />
140 TYP$(3)="INT/FIX"<br />
150 TYP$(4)="INT/VAR"<br />
160 TYP$(5)="PROGRAM"<br />
170 INPUT "MASTER DISK(1-3)?":A<br />
180 A=INT(A)<br />
190 IF A<1 THEN 170<br />
200 IF A>3 THEN 170<br />
210 OPEN #1:"DSK"&STR$(A)&".",INPUT,RELATIVE,INTERNAL<br />
220 INPUT #1:A$,J,J,K<br />
230 PRINT "DSK";STR$(A);" -DISK NAME= ";A$:"FREE= ";K;"USED= ";J-K<br />
240 PRINT:"FILE NAME SIZE TYPE P":"__________ ______ ________ _"<br />
250 FOR LOOP=1 TO 127<br />
260 INPUT #1:A$,A,J,K<br />
270 IF LEN(A$)=0 THEN 350<br />
280 PRINT:A$;TAB(12);J;TAB(19);TYP$(ABS(A));<br />
290 IF ABS(A)=5 THEN 320<br />
300 B$=" "&STR$(K)<br />
310 PRINT SEG$(B$,LEN(B$)-2,3);<br />
320 IF A>0 THEN 340<br />
330 PRINT TAB(28);"P";<br />
340 NEXT LOOP<br />
350 CLOSE #1<br />
<br />
You can easily expand this program to consider subdirectories; just replace the number input in line 170-200 by a direct string input and open the given path name in line 210. <br />
<br />
Also, directories can be identified in the listing by extending the set of types. Type 6 represents a directory. Line 110 expands the array, 161 adds the mapping of type 6 to the label to print. Line 290 must be altered to skip printing the record length as was done for PROGRAM type files.<br />
<br />
100 CALL CLEAR<br />
110 DIM TYP$(6)<br />
120 TYP$(1)="DIS/FIX"<br />
130 TYP$(2)="DIS/VAR"<br />
140 TYP$(3)="INT/FIX"<br />
150 TYP$(4)="INT/VAR"<br />
160 TYP$(5)="PROGRAM"<br />
161 TYP$(6)="DIR "<br />
170 INPUT "DEVICE?":D$<br />
210 OPEN #1:D$&".",INPUT,RELATIVE,INTERNAL<br />
220 INPUT #1:A$,J,J,K<br />
230 PRINT D$;" -VOL=";A$:"FREE=";K;"USED=";J-K<br />
240 PRINT:"FILE NAME SIZE TYPE P":"__________ ____ __________ _"<br />
250 FOR LOOP=1 TO 127<br />
260 INPUT #1:A$,A,J,K<br />
270 IF LEN(A$)=0 THEN 350<br />
280 PRINT:A$;TAB(12);J;TAB(17);TYP$(ABS(A));<br />
290 IF ABS(A)>=5 THEN 320<br />
300 B$=" "&STR$(K)<br />
310 PRINT SEG$(B$,LEN(B$)-2,3);<br />
320 IF A>0 THEN 340<br />
330 PRINT TAB(28);"P";<br />
340 NEXT LOOP<br />
350 CLOSE #1<br />
<br />
[[Category:Programming]]</div>Jedimatt42http://www.ninerpedia.org/index.php?title=Booting_MDOS_from_Horizon_Ramdisk&diff=50329Booting MDOS from Horizon Ramdisk2020-06-02T19:28:54Z<p>Jedimatt42: </p>
<hr />
<div>[[MDOS 6.50]] supports booting 'SYSTEM/SYS' from a Horizon or SNUG ramdisk at crubase >1400.<br />
<br />
== Limitations ==<br />
<br />
* The ramdisk disk must be assigned DSK6 during the boot process<br />
* Crubase >1400 should be used. (Others not tested, there is evidence that they are known not to work for booting: https://atariage.com/forums/topic/307339-i-need-a-new-users-guide-to-mdos-and-the-last-35-years/?do=findComment&comment=4551765 )<br />
* Size of ramdisk is limited to 800k without extra hacking<br />
<br />
== Requirements ==<br />
<br />
Easy path:<br />
<br />
* GeneveOpSys650-redistributionpermitted2020.dsk - https://atariage.com/forums/topic/307339-i-need-a-new-users-guide-to-mdos-and-the-last-35-years/?do=findComment&comment=4552847<br />
<br />
or a little more work:<br />
<br />
* [[FORM123]] - https://atariage.com/forums/applications/core/interface/file/attachment.php?id=735056<br />
* [[MDOS 6.50]] SYSTEM/SYS - http://ftp.whtech.com/Geneve/GeneveOS_650_redist.dsk<br />
<br />
and<br />
<br />
* The ability to boot into MDOS from some other device, such as a floppy on DSK1.<br />
* The system is not configured to boot something else before the [[Horizon Ramdisk]] see [[Geneve BOOT Order]]<br />
<br />
=== Formatting ===<br />
<br />
# Set the CRUBASE of your Horizon ramdisk to >1400<br />
# Create a disk to boot the [[Geneve]] from that contains SYSTEM/SYS from [[MDOS 6.50]], [[CYA]], CYB, CYC, and [[FORM123]]. Or just use a copy of GeneveOpSys650-redistributionpermitted2020.dsk<br />
# Boot to MDOS from you floppy on DSK1.<br />
# Load the ramdisk formatting tool: FORM123 ''Note: the FORM123 tool menus expect uppercase letters''<br />
# Select A "AUTOSCAN CRU LOCATIONS >1200 thru >1900".<br />
# Answer Y to "Format 16 Bit Ramdisk at CRU >1401 (Y/N)?"<br />
# Answer Y to "Set disk to boot MDOS >1400 (Y/N)?"<br />
# Answer Y to "Load SYSTEM/SYS From Disk to Ramdisk (Y/N)?"<br />
# Assuming you booted SYSTEM/SYS from DSK1, Answer 1 to "Select disk drive to load from(1-9)?"<br />
# Once it is finished copying - "Press Anykey To Continue" <br />
# Select X to exit back to MDOS.<br />
<br />
At this point you should be able to see the ramdisk and that it has SYSTEM/SYS on it. Perform DIR DSK8. You should see a listing with Volume name "RAMDSK1401", and a single file: "SYSTEM/SYS". The free space should be 2684 sectors. It should be able to boot, however it won't be able to find an AUTOEXEC on the ramdisk yet. <br />
<br />
# Verify that it can boot, press CTRL-SHIFT-SHIFT. <br />
<br />
It should load SYSTEM/SYS much faster than you would see from your floppy. When booting is complete, you will still be left at an A:\> prompt. That can be changed later.<br />
<br />
=== Configure Device Map ===<br />
<br />
''Running CYA can be skipped if using the SYSTEM/SYS from GeneveOpSys650-redistributionpermitted2020.dsk. Skip to the'' '''Create AUTOEXEC''' ''section''<br />
<br />
We need to now run CYA to configure the drive mapping during boot, so that it is DSK6.<br />
<br />
# give DSK8 a drive letter to make it easier to work with in CYA - assign E=DSK8: <br />
# Load MDOS into CYA for configuration: A:\CYA E:\SYSTEM"/"SYS<br />
# Select D for "(D)rive remap/assign"<br />
# Select R to map the 16-bit ramdisk into DSK6.<br />
# Select 6, then N<br />
# Press ESC to return up to previous menu.<br />
# Press ESC to return to the top menu.<br />
# Select S to "(S)ave SYSTEM/SYS"<br />
# Press ENTER to save to the ramdisk that we loaded it from. <br />
# Select Q to "(Q)uit CYA", and respond with Y<br />
<br />
=== Create AUTOEXEC ===<br />
<br />
If you skipped the previous section, assign a drive letter to DSK6<br />
<br />
# Run: ASSIGN E=DSK6:<br />
<br />
Now, it should be able to boot off the Horizon ramdisk and find an AUTOEXEC on that ramdisk. So let's create an AUTOEXEC. E: should still be assigned to your ramdisk at this stage.<br />
<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ECHO RAMDISK<br />
# Press CTRL-Z to close the file.<br />
<br />
Now if press CTRL-SHIFT-SHIFT, it should boot from the ramdisk, and we should see 'RAMDISK' printed as evidence that it loaded the AUTOEXEC from the ramdisk. The ramdisk itself still doesn't have a drive letter assigned. We can correct that in our AUTOEXEC<br />
<br />
# Run: ASSIGN E=DSK6:<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ASSIGN E=DSK6:<br />
# Enter: E:<br />
# Enter: VER<br />
# Press CTRL-Z<br />
<br />
Now when you reboot, you should have the ramdisk available as drive letter E:, and you will be on drive E: by default.<br />
<br />
== Notes ==<br />
<br />
The [[MDOS 6.50]] redistribution disk image comes with [[FORM3MEG]], however the Geneve 0.98 and 1.00 boot roms are not capable of booting from the large volume it creates. It can be used to format an '8-bit' (256K) ramdisk that can boot, or '16-bit' larger volume that can be accessed after boot. There alleged to be an article in [[Micropendium]] describing how to boot from the fully allocated ramdisk. http://ftp.whtech.com/magazines/micropendium/mp99last.pdf<br />
<br />
[[MDOS 6.70rc2]] will work with a 256K (8bit) ramdisk. With crubase >1400, the 8bit ramdisk device is mapped to DSK6 by default and allows MDOS to find the DSK6.AUTOEXEC. [[MDOS 6.70rc2]] does not have a supporting [[CYA]] program to alter assignements.</div>Jedimatt42http://www.ninerpedia.org/index.php?title=Booting_MDOS_from_Horizon_Ramdisk&diff=50328Booting MDOS from Horizon Ramdisk2020-06-01T02:02:40Z<p>Jedimatt42: </p>
<hr />
<div>[[MDOS 6.50]] supports booting 'SYSTEM/SYS' from a Horizon or SNUG ramdisk at crubase >1400.<br />
<br />
== Limitations ==<br />
<br />
* The ramdisk disk must be assigned DSK6 during the boot process<br />
* Crubase >1400 should be used. (Others not tested)<br />
* Size of ramdisk is limited to 800k without extra hacking<br />
<br />
== Requirements ==<br />
<br />
Easy path:<br />
<br />
* GeneveOpSys650-redistributionpermitted2020.dsk - https://atariage.com/forums/topic/307339-i-need-a-new-users-guide-to-mdos-and-the-last-35-years/?do=findComment&comment=4552847<br />
<br />
or a little more work:<br />
<br />
* [[FORM123]] - https://atariage.com/forums/applications/core/interface/file/attachment.php?id=735056<br />
* [[MDOS 6.50]] SYSTEM/SYS - http://ftp.whtech.com/Geneve/GeneveOS_650_redist.dsk<br />
<br />
and<br />
<br />
* The ability to boot into MDOS from some other device, such as a floppy on DSK1.<br />
* The system is not configured to boot something else before the [[Horizon Ramdisk]] see [[Geneve BOOT Order]]<br />
<br />
=== Formatting ===<br />
<br />
# Set the CRUBASE of your Horizon ramdisk to >1400<br />
# Create a disk to boot the [[Geneve]] from that contains SYSTEM/SYS from [[MDOS 6.50]], [[CYA]], CYB, CYC, and [[FORM123]]. Or just use a copy of GeneveOpSys650-redistributionpermitted2020.dsk<br />
# Boot to MDOS from you floppy on DSK1.<br />
# Load the ramdisk formatting tool: FORM123 ''Note: the FORM123 tool menus expect uppercase letters''<br />
# Select A "AUTOSCAN CRU LOCATIONS >1200 thru >1900".<br />
# Answer Y to "Format 16 Bit Ramdisk at CRU >1401 (Y/N)?"<br />
# Answer Y to "Set disk to boot MDOS >1400 (Y/N)?"<br />
# Answer Y to "Load SYSTEM/SYS From Disk to Ramdisk (Y/N)?"<br />
# Assuming you booted SYSTEM/SYS from DSK1, Answer 1 to "Select disk drive to load from(1-9)?"<br />
# Once it is finished copying - "Press Anykey To Continue" <br />
# Select X to exit back to MDOS.<br />
<br />
At this point you should be able to see the ramdisk and that it has SYSTEM/SYS on it. Perform DIR DSK8. You should see a listing with Volume name "RAMDSK1401", and a single file: "SYSTEM/SYS". The free space should be 2684 sectors. It should be able to boot, however it won't be able to find an AUTOEXEC on the ramdisk yet. <br />
<br />
# Verify that it can boot, press CTRL-SHIFT-SHIFT. <br />
<br />
It should load SYSTEM/SYS much faster than you would see from your floppy. When booting is complete, you will still be left at an A:\> prompt. That can be changed later.<br />
<br />
=== Configure Device Map ===<br />
<br />
''Running CYA can be skipped if using the SYSTEM/SYS from GeneveOpSys650-redistributionpermitted2020.dsk. Skip to the'' '''Create AUTOEXEC''' ''section''<br />
<br />
We need to now run CYA to configure the drive mapping during boot, so that it is DSK6.<br />
<br />
# give DSK8 a drive letter to make it easier to work with in CYA - assign E=DSK8: <br />
# Load MDOS into CYA for configuration: A:\CYA E:\SYSTEM"/"SYS<br />
# Select D for "(D)rive remap/assign"<br />
# Select R to map the 16-bit ramdisk into DSK6.<br />
# Select 6, then N<br />
# Press ESC to return up to previous menu.<br />
# Press ESC to return to the top menu.<br />
# Select S to "(S)ave SYSTEM/SYS"<br />
# Press ENTER to save to the ramdisk that we loaded it from. <br />
# Select Q to "(Q)uit CYA", and respond with Y<br />
<br />
=== Create AUTOEXEC ===<br />
<br />
If you skipped the previous section, assign a drive letter to DSK6<br />
<br />
# Run: ASSIGN E=DSK6:<br />
<br />
Now, it should be able to boot off the Horizon ramdisk and find an AUTOEXEC on that ramdisk. So let's create an AUTOEXEC. E: should still be assigned to your ramdisk at this stage.<br />
<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ECHO RAMDISK<br />
# Press CTRL-Z to close the file.<br />
<br />
Now if press CTRL-SHIFT-SHIFT, it should boot from the ramdisk, and we should see 'RAMDISK' printed as evidence that it loaded the AUTOEXEC from the ramdisk. The ramdisk itself still doesn't have a drive letter assigned. We can correct that in our AUTOEXEC<br />
<br />
# Run: ASSIGN E=DSK6:<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ASSIGN E=DSK6:<br />
# Enter: E:<br />
# Enter: VER<br />
# Press CTRL-Z<br />
<br />
Now when you reboot, you should have the ramdisk available as drive letter E:, and you will be on drive E: by default.<br />
<br />
== Notes ==<br />
<br />
The [[MDOS 6.50]] redistribution disk image comes with [[FORM3MEG]], however the Geneve 0.98 and 1.00 boot roms are not capable of booting from the large volume it creates. It can be used to format an '8-bit' (256K) ramdisk that can boot, or '16-bit' larger volume that can be accessed after boot. There alleged to be an article in [[Micropendium]] describing how to boot from the fully allocated ramdisk. http://ftp.whtech.com/magazines/micropendium/mp99last.pdf<br />
<br />
[[MDOS 6.70rc2]] will work with a 256K (8bit) ramdisk. With crubase >1400, the 8bit ramdisk device is mapped to DSK6 by default and allows MDOS to find the DSK6.AUTOEXEC. [[MDOS 6.70rc2]] does not have a supporting [[CYA]] program to alter assignements.</div>Jedimatt42http://www.ninerpedia.org/index.php?title=Booting_MDOS_from_Horizon_Ramdisk&diff=50327Booting MDOS from Horizon Ramdisk2020-06-01T02:01:30Z<p>Jedimatt42: </p>
<hr />
<div>[[MDOS 6.50]] supports booting 'SYSTEM/SYS' from a Horizon or SNUG ramdisk at crubase >1400.<br />
<br />
== Limitations ==<br />
<br />
* The ramdisk disk must be assigned DSK6 during the boot process<br />
* Crubase >1400 should be used. (Others not tested)<br />
* Size of ramdisk is limited to 800k without extra hacking<br />
<br />
== Requirements ==<br />
<br />
* GeneveOpSys650-redistributionpermitted2020.dsk - https://atariage.com/forums/topic/307339-i-need-a-new-users-guide-to-mdos-and-the-last-35-years/?do=findComment&comment=4552847<br />
<br />
or<br />
<br />
* [[FORM123]] - https://atariage.com/forums/applications/core/interface/file/attachment.php?id=735056<br />
* [[MDOS 6.50]] SYSTEM/SYS - http://ftp.whtech.com/Geneve/GeneveOS_650_redist.dsk<br />
<br />
and<br />
<br />
* The ability to boot into MDOS from some other device, such as a floppy on DSK1.<br />
* The system is not configured to boot something else before the [[Horizon Ramdisk]] see [[Geneve BOOT Order]]<br />
<br />
=== Formatting ===<br />
<br />
# Set the CRUBASE of your Horizon ramdisk to >1400<br />
# Create a disk to boot the [[Geneve]] from that contains SYSTEM/SYS from [[MDOS 6.50]], [[CYA]], CYB, CYC, and [[FORM123]]. Or just use a copy of GeneveOpSys650-redistributionpermitted2020.dsk<br />
# Boot to MDOS from you floppy on DSK1.<br />
# Load the ramdisk formatting tool: FORM123 ''Note: the FORM123 tool menus expect uppercase letters''<br />
# Select A "AUTOSCAN CRU LOCATIONS >1200 thru >1900".<br />
# Answer Y to "Format 16 Bit Ramdisk at CRU >1401 (Y/N)?"<br />
# Answer Y to "Set disk to boot MDOS >1400 (Y/N)?"<br />
# Answer Y to "Load SYSTEM/SYS From Disk to Ramdisk (Y/N)?"<br />
# Assuming you booted SYSTEM/SYS from DSK1, Answer 1 to "Select disk drive to load from(1-9)?"<br />
# Once it is finished copying - "Press Anykey To Continue" <br />
# Select X to exit back to MDOS.<br />
<br />
At this point you should be able to see the ramdisk and that it has SYSTEM/SYS on it. Perform DIR DSK8. You should see a listing with Volume name "RAMDSK1401", and a single file: "SYSTEM/SYS". The free space should be 2684 sectors. It should be able to boot, however it won't be able to find an AUTOEXEC on the ramdisk yet. <br />
<br />
# Verify that it can boot, press CTRL-SHIFT-SHIFT. <br />
<br />
It should load SYSTEM/SYS much faster than you would see from your floppy. When booting is complete, you will still be left at an A:\> prompt. That can be changed later.<br />
<br />
=== Configure Device Map ===<br />
<br />
''Running CYA can be skipped if using the SYSTEM/SYS from GeneveOpSys650-redistributionpermitted2020.dsk. Skip to the'' '''Create AUTOEXEC''' ''section''<br />
<br />
We need to now run CYA to configure the drive mapping during boot, so that it is DSK6.<br />
<br />
# give DSK8 a drive letter to make it easier to work with in CYA - assign E=DSK8: <br />
# Load MDOS into CYA for configuration: A:\CYA E:\SYSTEM"/"SYS<br />
# Select D for "(D)rive remap/assign"<br />
# Select R to map the 16-bit ramdisk into DSK6.<br />
# Select 6, then N<br />
# Press ESC to return up to previous menu.<br />
# Press ESC to return to the top menu.<br />
# Select S to "(S)ave SYSTEM/SYS"<br />
# Press ENTER to save to the ramdisk that we loaded it from. <br />
# Select Q to "(Q)uit CYA", and respond with Y<br />
<br />
=== Create AUTOEXEC ===<br />
<br />
If you skipped the previous section, assign a drive letter to DSK6<br />
<br />
# Run: ASSIGN E=DSK6:<br />
<br />
Now, it should be able to boot off the Horizon ramdisk and find an AUTOEXEC on that ramdisk. So let's create an AUTOEXEC. E: should still be assigned to your ramdisk at this stage.<br />
<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ECHO RAMDISK<br />
# Press CTRL-Z to close the file.<br />
<br />
Now if press CTRL-SHIFT-SHIFT, it should boot from the ramdisk, and we should see 'RAMDISK' printed as evidence that it loaded the AUTOEXEC from the ramdisk. The ramdisk itself still doesn't have a drive letter assigned. We can correct that in our AUTOEXEC<br />
<br />
# Run: ASSIGN E=DSK6:<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ASSIGN E=DSK6:<br />
# Enter: E:<br />
# Enter: VER<br />
# Press CTRL-Z<br />
<br />
Now when you reboot, you should have the ramdisk available as drive letter E:, and you will be on drive E: by default.<br />
<br />
== Notes ==<br />
<br />
The [[MDOS 6.50]] redistribution disk image comes with [[FORM3MEG]], however the Geneve 0.98 and 1.00 boot roms are not capable of booting from the large volume it creates. It can be used to format an '8-bit' (256K) ramdisk that can boot, or '16-bit' larger volume that can be accessed after boot. There alleged to be an article in [[Micropendium]] describing how to boot from the fully allocated ramdisk. http://ftp.whtech.com/magazines/micropendium/mp99last.pdf<br />
<br />
[[MDOS 6.70rc2]] will work with a 256K (8bit) ramdisk. With crubase >1400, the 8bit ramdisk device is mapped to DSK6 by default and allows MDOS to find the DSK6.AUTOEXEC. [[MDOS 6.70rc2]] does not have a supporting [[CYA]] program to alter assignements.</div>Jedimatt42http://www.ninerpedia.org/index.php?title=Booting_MDOS_from_Horizon_Ramdisk&diff=50326Booting MDOS from Horizon Ramdisk2020-05-31T21:38:39Z<p>Jedimatt42: </p>
<hr />
<div>[[MDOS 6.50]] supports booting 'SYSTEM/SYS' from a Horizon or SNUG ramdisk at crubase >1400.<br />
<br />
== Limitations ==<br />
<br />
* The ramdisk disk must be assigned DSK6 during the boot process<br />
* Crubase >1400 should be used. (Others not tested)<br />
* Size of ramdisk is limited to 800k without extra hacking<br />
<br />
== Requirements ==<br />
<br />
* GeneveOpSys650-redistributionpermitted2020.dsk<br />
<br />
or<br />
<br />
* [[FORM123]] - https://atariage.com/forums/applications/core/interface/file/attachment.php?id=735056<br />
* [[MDOS 6.50]] SYSTEM/SYS - http://ftp.whtech.com/Geneve/GeneveOS_650_redist.dsk<br />
<br />
and<br />
<br />
* The ability to boot into MDOS from some other device, such as a floppy on DSK1.<br />
* The system is not configured to boot something else before the [[Horizon Ramdisk]] see [[Geneve BOOT Order]]<br />
<br />
=== Formatting ===<br />
<br />
# Set the CRUBASE of your Horizon ramdisk to >1400<br />
# Create a disk to boot the [[Geneve]] from that contains SYSTEM/SYS from [[MDOS 6.50]], [[CYA]], CYB, CYC, and [[FORM123]]. Or just use a copy of GeneveOpSys650-redistributionpermitted2020.dsk<br />
# Boot to MDOS from you floppy on DSK1.<br />
# Load the ramdisk formatting tool: FORM123 ''Note: the FORM123 tool menus expect uppercase letters''<br />
# Select A "AUTOSCAN CRU LOCATIONS >1200 thru >1900".<br />
# Answer Y to "Format 16 Bit Ramdisk at CRU >1401 (Y/N)?"<br />
# Answer Y to "Set disk to boot MDOS >1400 (Y/N)?"<br />
# Answer Y to "Load SYSTEM/SYS From Disk to Ramdisk (Y/N)?"<br />
# Assuming you booted SYSTEM/SYS from DSK1, Answer 1 to "Select disk drive to load from(1-9)?"<br />
# Once it is finished copying - "Press Anykey To Continue" <br />
# Select X to exit back to MDOS.<br />
<br />
At this point you should be able to see the ramdisk and that it has SYSTEM/SYS on it. Perform DIR DSK8. You should see a listing with Volume name "RAMDSK1401", and a single file: "SYSTEM/SYS". The free space should be 2684 sectors. It should be able to boot, however it won't be able to find an AUTOEXEC on the ramdisk yet. <br />
<br />
# Verify that it can boot, press CTRL-SHIFT-SHIFT. <br />
<br />
It should load SYSTEM/SYS much faster than you would see from your floppy. When booting is complete, you will still be left at an A:\> prompt. That can be changed later.<br />
<br />
=== Configure Device Map ===<br />
<br />
''Running CYA can be skipped if using the SYSTEM/SYS from GeneveOpSys650-redistributionpermitted2020.dsk. Skip to the'' '''Create AUTOEXEC''' ''section''<br />
<br />
We need to now run CYA to configure the drive mapping during boot, so that it is DSK6.<br />
<br />
# give DSK8 a drive letter to make it easier to work with in CYA - assign E=DSK8: <br />
# Load MDOS into CYA for configuration: A:\CYA E:\SYSTEM"/"SYS<br />
# Select D for "(D)rive remap/assign"<br />
# Select R to map the 16-bit ramdisk into DSK6.<br />
# Select 6, then N<br />
# Press ESC to return up to previous menu.<br />
# Press ESC to return to the top menu.<br />
# Select S to "(S)ave SYSTEM/SYS"<br />
# Press ENTER to save to the ramdisk that we loaded it from. <br />
# Select Q to "(Q)uit CYA", and respond with Y<br />
<br />
=== Create AUTOEXEC ===<br />
<br />
If you skipped the previous section, assign a drive letter to DSK6<br />
<br />
# Run: ASSIGN E=DSK6:<br />
<br />
Now, it should be able to boot off the Horizon ramdisk and find an AUTOEXEC on that ramdisk. So let's create an AUTOEXEC. E: should still be assigned to your ramdisk at this stage.<br />
<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ECHO RAMDISK<br />
# Press CTRL-Z to close the file.<br />
<br />
Now if press CTRL-SHIFT-SHIFT, it should boot from the ramdisk, and we should see 'RAMDISK' printed as evidence that it loaded the AUTOEXEC from the ramdisk. The ramdisk itself still doesn't have a drive letter assigned. We can correct that in our AUTOEXEC<br />
<br />
# Run: ASSIGN E=DSK6:<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ASSIGN E=DSK6:<br />
# Enter: E:<br />
# Enter: VER<br />
# Press CTRL-Z<br />
<br />
Now when you reboot, you should have the ramdisk available as drive letter E:, and you will be on drive E: by default.<br />
<br />
== Notes ==<br />
<br />
The [[MDOS 6.50]] redistribution disk image comes with [[FORM3MEG]], however the Geneve 0.98 and 1.00 boot roms are not capable of booting from the large volume it creates. It can be used to format an '8-bit' (256K) ramdisk that can boot, or '16-bit' larger volume that can be accessed after boot. There alleged to be an article in [[Micropendium]] describing how to boot from the fully allocated ramdisk. http://ftp.whtech.com/magazines/micropendium/mp99last.pdf<br />
<br />
[[MDOS 6.70rc2]] will work with a 256K (8bit) ramdisk. With crubase >1400, the 8bit ramdisk device is mapped to DSK6 by default and allows MDOS to find the DSK6.AUTOEXEC. [[MDOS 6.70rc2]] does not have a supporting [[CYA]] program to alter assignements.</div>Jedimatt42http://www.ninerpedia.org/index.php?title=Booting_MDOS_from_Horizon_Ramdisk&diff=50325Booting MDOS from Horizon Ramdisk2020-05-31T21:35:15Z<p>Jedimatt42: </p>
<hr />
<div>[[MDOS 6.50]] supports booting 'SYSTEM/SYS' from a Horizon or SNUG ramdisk at crubase >1400.<br />
<br />
== Limitations ==<br />
<br />
* The ramdisk disk must be assigned DSK6 during the boot process<br />
* Crubase >1400 should be used. (Others not tested)<br />
* Size of ramdisk is limited to 800k without extra hacking<br />
<br />
== Requirements ==<br />
<br />
* GeneveOpSys650-redistributionpermitted2020.dsk<br />
<br />
or<br />
<br />
* [[FORM123]] - https://atariage.com/forums/applications/core/interface/file/attachment.php?id=735056<br />
* [[MDOS 6.50]] SYSTEM/SYS - http://ftp.whtech.com/Geneve/GeneveOS_650_redist.dsk<br />
<br />
and<br />
<br />
* The ability to boot into MDOS from some other device, such as a floppy on DSK1.<br />
* The system is not configured to boot something else before the [[Horizon Ramdisk]] see [[Geneve BOOT Order]]<br />
<br />
=== Formatting ===<br />
<br />
# Set the CRUBASE of your Horizon ramdisk to >1400<br />
# Create a disk to boot the [[Geneve]] from that contains SYSTEM/SYS from [[MDOS 6.50]], [[CYA]], CYB, CYC, and [[FORM123]]. Or just use a copy of GeneveOpSys650-redistributionpermitted2020.dsk<br />
# Boot to MDOS from you floppy on DSK1.<br />
# Load the ramdisk formatting tool: FORM123 ''Note: the FORM123 tool menus expect uppercase letters''<br />
# Select A "AUTOSCAN CRU LOCATIONS >1200 thru >1900".<br />
# Answer Y to "Format 16 Bit Ramdisk at CRU >1401 (Y/N)?"<br />
# Answer Y to "Set disk to boot MDOS >1400 (Y/N)?"<br />
# Answer Y to "Load SYSTEM/SYS From Disk to Ramdisk (Y/N)?"<br />
# Assuming you booted SYSTEM/SYS from DSK1, Answer 1 to "Select disk drive to load from(1-9)?"<br />
# Once it is finished copying - "Press Anykey To Continue" <br />
# Select X to exit back to MDOS.<br />
<br />
At this point you should be able to see the ramdisk and that it has SYSTEM/SYS on it. Perform DIR DSK8. You should see a listing with Volume name "RAMDSK1401", and a single file: "SYSTEM/SYS". The free space should be 2684 sectors. It should be able to boot, however it won't be able to find an AUTOEXEC on the ramdisk yet. <br />
<br />
# Verify that it can boot, press CTRL-SHIFT-SHIFT. <br />
<br />
It should load SYSTEM/SYS much faster than you would see from your floppy. When booting is complete, you will still be left at an A:\> prompt. That can be changed later.<br />
<br />
=== Configure Device Map ===<br />
<br />
''Running CYA can be skipped if using the SYSTEM/SYS from GeneveOpSys650-redistributionpermitted2020.dsk. Skip to the Create AUTOEXEC section''<br />
<br />
We need to now run CYA to configure the drive mapping during boot, so that it is DSK6.<br />
<br />
# give DSK8 a drive letter to make it easier to work with in CYA - assign E=DSK8: <br />
# Load MDOS into CYA for configuration: A:\CYA E:\SYSTEM"/"SYS<br />
# Select D for "(D)rive remap/assign"<br />
# Select R to map the 16-bit ramdisk into DSK6.<br />
# Select 6, then N<br />
# Press ESC to return up to previous menu.<br />
# Press ESC to return to the top menu.<br />
# Select S to "(S)ave SYSTEM/SYS"<br />
# Press ENTER to save to the ramdisk that we loaded it from. <br />
# Select Q to "(Q)uit CYA", and respond with Y<br />
<br />
=== Create AUTOEXEC ===<br />
<br />
If you skipped the previous section, assign a drive letter to DSK6<br />
<br />
# Run: ASSIGN E=DSK6:<br />
<br />
Now, it should be able to boot off the Horizon ramdisk and find an AUTOEXEC on that ramdisk. So let's create an AUTOEXEC. E: should still be assigned to your ramdisk at this stage.<br />
<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ECHO RAMDISK<br />
# Press CTRL-Z to close the file.<br />
<br />
Now if press CTRL-SHIFT-SHIFT, it should boot from the ramdisk, and we should see 'RAMDISK' printed as evidence that it loaded the AUTOEXEC from the ramdisk. The ramdisk itself still doesn't have a drive letter assigned. We can correct that in our AUTOEXEC<br />
<br />
# Run: ASSIGN E=DSK6:<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ASSIGN E=DSK6:<br />
# Enter: E:<br />
# Enter: VER<br />
# Press CTRL-Z<br />
<br />
Now when you reboot, you should have the ramdisk available as drive letter E:, and you will be on drive E: by default.<br />
<br />
== Notes ==<br />
<br />
The [[MDOS 6.50]] redistribution disk image comes with [[FORM3MEG]], however the Geneve 0.98 and 1.00 boot roms are not capable of booting from the large volume it creates. It can be used to format an '8-bit' (256K) ramdisk that can boot, or '16-bit' larger volume that can be accessed after boot. There alleged to be an article in [[Micropendium]] describing how to boot from the fully allocated ramdisk. http://ftp.whtech.com/magazines/micropendium/mp99last.pdf<br />
<br />
[[MDOS 6.70rc2]] will work with a 256K (8bit) ramdisk. With crubase >1400, the 8bit ramdisk device is mapped to DSK6 by default and allows MDOS to find the DSK6.AUTOEXEC. [[MDOS 6.70rc2]] does not have a supporting [[CYA]] program to alter assignements.</div>Jedimatt42http://www.ninerpedia.org/index.php?title=Booting_MDOS_from_Horizon_Ramdisk&diff=50324Booting MDOS from Horizon Ramdisk2020-05-31T21:34:07Z<p>Jedimatt42: </p>
<hr />
<div>[[MDOS 6.50]] supports booting 'SYSTEM/SYS' from a Horizon or SNUG ramdisk at crubase >1400.<br />
<br />
== Limitations ==<br />
<br />
* The ramdisk disk must be assigned DSK6 during the boot process<br />
* Crubase >1400 should be used. (Others not tested)<br />
* Size of ramdisk is limited to 800k without extra hacking<br />
<br />
== Requirements ==<br />
<br />
* GeneveOpSys650-redistributionpermitted2020.dsk<br />
<br />
or<br />
<br />
* [[FORM123]] - https://atariage.com/forums/applications/core/interface/file/attachment.php?id=735056<br />
* [[MDOS 6.50]] SYSTEM/SYS - http://ftp.whtech.com/Geneve/GeneveOS_650_redist.dsk<br />
<br />
and<br />
<br />
* The ability to boot into MDOS from some other device, such as a floppy on DSK1.<br />
* The system is not configured to boot something else before the [[Horizon Ramdisk]] see [[Geneve BOOT Order]]<br />
<br />
=== Formatting ===<br />
<br />
# Set the CRUBASE of your Horizon ramdisk to >1400<br />
# Create a disk to boot the [[Geneve]] from that contains SYSTEM/SYS from [[MDOS 6.50]], [[CYA]], CYB, CYC, and [[FORM123]]. Or just use a copy of GeneveOpSys650-redistributionpermitted2020.dsk<br />
# Boot to MDOS from you floppy on DSK1.<br />
# Load the ramdisk formatting tool: FORM123 ''Note: the FORM123 tool menus expect uppercase letters''<br />
# Select A "AUTOSCAN CRU LOCATIONS >1200 thru >1900".<br />
# Answer Y to "Format 16 Bit Ramdisk at CRU >1401 (Y/N)?"<br />
# Answer Y to "Set disk to boot MDOS >1400 (Y/N)?"<br />
# Answer Y to "Load SYSTEM/SYS From Disk to Ramdisk (Y/N)?"<br />
# Assuming you booted SYSTEM/SYS from DSK1, Answer 1 to "Select disk drive to load from(1-9)?"<br />
# Once it is finished copying - "Press Anykey To Continue" <br />
# Select X to exit back to MDOS.<br />
<br />
At this point you should be able to see the ramdisk and that it has SYSTEM/SYS on it. Perform DIR DSK8. You should see a listing with Volume name "RAMDSK1401", and a single file: "SYSTEM/SYS". The free space should be 2684 sectors. It should be able to boot, however it won't be able to find an AUTOEXEC on the ramdisk yet. <br />
<br />
# Verify that it can boot, press CTRL-SHIFT-SHIFT. <br />
<br />
It should load SYSTEM/SYS much faster than you would see from your floppy. When booting is complete, you will still be left at an A:\> prompt. That can be changed later.<br />
<br />
=== Configure Device Map ===<br />
<br />
''Running CYA can be skipped if using the SYSTEM/SYS from GeneveOpSys650-redistributionpermitted2020.dsk. Skip to the Create AUTOEXEC section''<br />
<br />
We need to now run CYA to configure the drive mapping during boot, so that it is DSK6.<br />
<br />
# give DSK8 a drive letter to make it easier to work with in CYA - assign E=DSK8: <br />
# Load MDOS into CYA for configuration: A:\CYA E:\SYSTEM"/"SYS<br />
# Select D for "(D)rive remap/assign"<br />
# Select R to map the 16-bit ramdisk into DSK6.<br />
# Select 6, then N<br />
# Press ESC to return up to previous menu.<br />
# Press ESC to return to the top menu.<br />
# Select S to "(S)ave SYSTEM/SYS"<br />
# Press ENTER to save to the ramdisk that we loaded it from. <br />
# Select Q to "(Q)uit CYA", and respond with Y<br />
<br />
=== Create AUTOEXEC ===<br />
<br />
If you skipped the previous section, assign a drive letter to DSK6<br />
<br />
# Run: ASSIGN E=DSK6:<br />
<br />
Now, it should be able to boot off the Horizon ramdisk and find an AUTOEXEC on that ramdisk. So let's create an AUTOEXEC. E: should still be assigned to your ramdisk at this stage.<br />
<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ECHO RAMDISK<br />
# Press CTRL-Z to close the file.<br />
<br />
Now if press CTRL-SHIFT-SHIFT, it should boot from the ramdisk, and we should see 'RAMDISK' printed as evidence that it loaded the AUTOEXEC from the ramdisk. The ramdisk itself still doesn't have a drive letter assigned. We can correct that in our AUTOEXEC<br />
<br />
# Run: ASSIGN E=DSK6:<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ASSIGN E=DSK6:<br />
# Enter: E:<br />
# Enter: VER<br />
# Press CTRL-Z<br />
<br />
Now when you reboot, you should have the ramdisk available as drive letter E:, and you will be on drive E: by default.<br />
<br />
== Notes ==<br />
<br />
The [[MDOS 6.50]] redistribution disk image comes with [[FORM3MEG]], however the Geneve 0.98 and 1.00 boot roms are not capable of booting from the large volume it creates. It can be used to format an '8-bit' (256K) ramdisk that can boot, or '16-bit' larger volume that can be accessed after boot. There alleged to be an article in [[Micropendium]] describing how to boot from the fully allocated ramdisk. <br />
<br />
[[MDOS 6.70rc2]] will work with a 256K (8bit) ramdisk. With crubase >1400, the 8bit ramdisk device is mapped to DSK6 by default and allows MDOS to find the DSK6.AUTOEXEC. [[MDOS 6.70rc2]] does not have a supporting [[CYA]] program to alter assignements.</div>Jedimatt42http://www.ninerpedia.org/index.php?title=Booting_MDOS_from_Horizon_Ramdisk&diff=50323Booting MDOS from Horizon Ramdisk2020-05-31T21:32:10Z<p>Jedimatt42: /* Create AUTOEXEC */</p>
<hr />
<div>[[MDOS 6.50]] supports booting 'SYSTEM/SYS' from a Horizon or SNUG ramdisk at crubase >1400.<br />
<br />
== Limitations ==<br />
<br />
* The ramdisk disk must be assigned DSK6 during the boot process<br />
* Crubase >1400 should be used. (Others not tested)<br />
* Size of ramdisk is limited to 800k without extra hacking<br />
<br />
== Requirements ==<br />
<br />
* GeneveOpSys650-redistributionpermitted2020.dsk<br />
<br />
or<br />
<br />
* [[FORM123]] - https://atariage.com/forums/applications/core/interface/file/attachment.php?id=735056<br />
* [[MDOS 6.50]] SYSTEM/SYS - http://ftp.whtech.com/Geneve/GeneveOS_650_redist.dsk<br />
<br />
and<br />
<br />
* The ability to boot into MDOS from some other device, such as a floppy on DSK1.<br />
* The system is not configured to boot something else before the [[Horizon Ramdisk]] see [[Geneve BOOT Order]]<br />
<br />
=== Formatting ===<br />
<br />
# Set the CRUBASE of your Horizon ramdisk to >1400<br />
# Create a disk to boot the [[Geneve]] from that contains SYSTEM/SYS from [[MDOS 6.50]], [[CYA]], CYB, CYC, and [[FORM123]].<br />
# Boot to MDOS from you floppy on DSK1.<br />
# Load the ramdisk formatting tool: FORM123 ''Note: the FORM123 tool menus expect uppercase letters''<br />
# Select A "AUTOSCAN CRU LOCATIONS >1200 thru >1900".<br />
# Answer Y to "Format 16 Bit Ramdisk at CRU >1401 (Y/N)?"<br />
# Answer Y to "Set disk to boot MDOS >1400 (Y/N)?"<br />
# Answer Y to "Load SYSTEM/SYS From Disk to Ramdisk (Y/N)?"<br />
# Assuming you booted SYSTEM/SYS from DSK1, Answer 1 to "Select disk drive to load from(1-9)?"<br />
# Once it is finished copying - "Press Anykey To Continue" <br />
# Select X to exit back to MDOS.<br />
<br />
At this point you should be able to see the ramdisk and that it has SYSTEM/SYS on it. Perform DIR DSK8. You should see a listing with Volume name "RAMDSK1401", and a single file: "SYSTEM/SYS". The free space should be 2684 sectors. It should be able to boot, however it won't be able to find an AUTOEXEC on the ramdisk yet. <br />
<br />
# Verify that it can boot, press CTRL-SHIFT-SHIFT. <br />
<br />
It should load SYSTEM/SYS much faster than you would see from your floppy. When booting is complete, you will still be left at an A:\> prompt. That can be changed later.<br />
<br />
=== Configure Device Map ===<br />
<br />
''Running CYA can be skipped if using the SYSTEM/SYS from GeneveOpSys650-redistributionpermitted2020.dsk. Skip to the Create AUTOEXEC section''<br />
<br />
We need to now run CYA to configure the drive mapping during boot, so that it is DSK6.<br />
<br />
# give DSK8 a drive letter to make it easier to work with in CYA - assign E=DSK8: <br />
# Load MDOS into CYA for configuration: A:\CYA E:\SYSTEM"/"SYS<br />
# Select D for "(D)rive remap/assign"<br />
# Select R to map the 16-bit ramdisk into DSK6.<br />
# Select 6, then N<br />
# Press ESC to return up to previous menu.<br />
# Press ESC to return to the top menu.<br />
# Select S to "(S)ave SYSTEM/SYS"<br />
# Press ENTER to save to the ramdisk that we loaded it from. <br />
# Select Q to "(Q)uit CYA", and respond with Y<br />
<br />
=== Create AUTOEXEC ===<br />
<br />
If you skipped the previous section, assign a drive letter to DSK6<br />
<br />
# Run: ASSIGN E=DSK6:<br />
<br />
Now, it should be able to boot off the Horizon ramdisk and find an AUTOEXEC on that ramdisk. So let's create an AUTOEXEC. E: should still be assigned to your ramdisk at this stage.<br />
<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ECHO RAMDISK<br />
# Press CTRL-Z to close the file.<br />
<br />
Now if press CTRL-SHIFT-SHIFT, it should boot from the ramdisk, and we should see 'RAMDISK' printed as evidence that it loaded the AUTOEXEC from the ramdisk. The ramdisk itself still doesn't have a drive letter assigned. We can correct that in our AUTOEXEC<br />
<br />
# Run: ASSIGN E=DSK6:<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ASSIGN E=DSK6:<br />
# Enter: E:<br />
# Enter: VER<br />
# Press CTRL-Z<br />
<br />
Now when you reboot, you should have the ramdisk available as drive letter E:, and you will be on drive E: by default.<br />
<br />
== Notes ==<br />
<br />
The [[MDOS 6.50]] redistribution disk image comes with [[FORM3MEG]], however the Geneve 0.98 and 1.00 boot roms are not capable of booting from the large volume it creates. It can be used to format an '8-bit' (256K) ramdisk that can boot, or '16-bit' larger volume that can be accessed after boot. There alleged to be an article in [[Micropendium]] describing how to boot from the fully allocated ramdisk. <br />
<br />
[[MDOS 6.70rc2]] will work with a 256K (8bit) ramdisk. With crubase >1400, the 8bit ramdisk device is mapped to DSK6 by default and allows MDOS to find the DSK6.AUTOEXEC. [[MDOS 6.70rc2]] does not have a supporting [[CYA]] program to alter assignements.</div>Jedimatt42http://www.ninerpedia.org/index.php?title=Booting_MDOS_from_Horizon_Ramdisk&diff=50322Booting MDOS from Horizon Ramdisk2020-05-31T21:28:57Z<p>Jedimatt42: </p>
<hr />
<div>[[MDOS 6.50]] supports booting 'SYSTEM/SYS' from a Horizon or SNUG ramdisk at crubase >1400.<br />
<br />
== Limitations ==<br />
<br />
* The ramdisk disk must be assigned DSK6 during the boot process<br />
* Crubase >1400 should be used. (Others not tested)<br />
* Size of ramdisk is limited to 800k without extra hacking<br />
<br />
== Requirements ==<br />
<br />
* GeneveOpSys650-redistributionpermitted2020.dsk<br />
<br />
or<br />
<br />
* [[FORM123]] - https://atariage.com/forums/applications/core/interface/file/attachment.php?id=735056<br />
* [[MDOS 6.50]] SYSTEM/SYS - http://ftp.whtech.com/Geneve/GeneveOS_650_redist.dsk<br />
<br />
and<br />
<br />
* The ability to boot into MDOS from some other device, such as a floppy on DSK1.<br />
* The system is not configured to boot something else before the [[Horizon Ramdisk]] see [[Geneve BOOT Order]]<br />
<br />
=== Formatting ===<br />
<br />
# Set the CRUBASE of your Horizon ramdisk to >1400<br />
# Create a disk to boot the [[Geneve]] from that contains SYSTEM/SYS from [[MDOS 6.50]], [[CYA]], CYB, CYC, and [[FORM123]].<br />
# Boot to MDOS from you floppy on DSK1.<br />
# Load the ramdisk formatting tool: FORM123 ''Note: the FORM123 tool menus expect uppercase letters''<br />
# Select A "AUTOSCAN CRU LOCATIONS >1200 thru >1900".<br />
# Answer Y to "Format 16 Bit Ramdisk at CRU >1401 (Y/N)?"<br />
# Answer Y to "Set disk to boot MDOS >1400 (Y/N)?"<br />
# Answer Y to "Load SYSTEM/SYS From Disk to Ramdisk (Y/N)?"<br />
# Assuming you booted SYSTEM/SYS from DSK1, Answer 1 to "Select disk drive to load from(1-9)?"<br />
# Once it is finished copying - "Press Anykey To Continue" <br />
# Select X to exit back to MDOS.<br />
<br />
At this point you should be able to see the ramdisk and that it has SYSTEM/SYS on it. Perform DIR DSK8. You should see a listing with Volume name "RAMDSK1401", and a single file: "SYSTEM/SYS". The free space should be 2684 sectors. It should be able to boot, however it won't be able to find an AUTOEXEC on the ramdisk yet. <br />
<br />
# Verify that it can boot, press CTRL-SHIFT-SHIFT. <br />
<br />
It should load SYSTEM/SYS much faster than you would see from your floppy. When booting is complete, you will still be left at an A:\> prompt. That can be changed later.<br />
<br />
=== Configure Device Map ===<br />
<br />
''Running CYA can be skipped if using the SYSTEM/SYS from GeneveOpSys650-redistributionpermitted2020.dsk. Skip to the Create AUTOEXEC section''<br />
<br />
We need to now run CYA to configure the drive mapping during boot, so that it is DSK6.<br />
<br />
# give DSK8 a drive letter to make it easier to work with in CYA - assign E=DSK8: <br />
# Load MDOS into CYA for configuration: A:\CYA E:\SYSTEM"/"SYS<br />
# Select D for "(D)rive remap/assign"<br />
# Select R to map the 16-bit ramdisk into DSK6.<br />
# Select 6, then N<br />
# Press ESC to return up to previous menu.<br />
# Press ESC to return to the top menu.<br />
# Select S to "(S)ave SYSTEM/SYS"<br />
# Press ENTER to save to the ramdisk that we loaded it from. <br />
# Select Q to "(Q)uit CYA", and respond with Y<br />
<br />
=== Create AUTOEXEC ===<br />
<br />
Now, it should be able to boot off the Horizon ramdisk and find an AUTOEXEC on that ramdisk. So let's create an AUTOEXEC. E: should still be assigned to your ramdisk at this stage.<br />
<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ECHO RAMDISK<br />
# Press CTRL-Z to close the file.<br />
<br />
Now if press CTRL-SHIFT-SHIFT, it should boot from the ramdisk, and we should see 'RAMDISK' printed as evidence that it loaded the AUTOEXEC from the ramdisk. The ramdisk itself still doesn't have a drive letter assigned. We can correct that in our AUTOEXEC<br />
<br />
# Run: ASSIGN E=DSK6:<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ASSIGN E=DSK6:<br />
# Enter: E:<br />
# Enter: VER<br />
# Press CTRL-Z<br />
<br />
Now when you reboot, you should have the ramdisk available as drive letter E:, and you will be on drive E: by default.<br />
<br />
== Notes ==<br />
<br />
The [[MDOS 6.50]] redistribution disk image comes with [[FORM3MEG]], however the Geneve 0.98 and 1.00 boot roms are not capable of booting from the large volume it creates. It can be used to format an '8-bit' (256K) ramdisk that can boot, or '16-bit' larger volume that can be accessed after boot. There alleged to be an article in [[Micropendium]] describing how to boot from the fully allocated ramdisk. <br />
<br />
[[MDOS 6.70rc2]] will work with a 256K (8bit) ramdisk. With crubase >1400, the 8bit ramdisk device is mapped to DSK6 by default and allows MDOS to find the DSK6.AUTOEXEC. [[MDOS 6.70rc2]] does not have a supporting [[CYA]] program to alter assignements.</div>Jedimatt42http://www.ninerpedia.org/index.php?title=Booting_MDOS_from_Horizon_Ramdisk&diff=50321Booting MDOS from Horizon Ramdisk2020-05-31T16:43:02Z<p>Jedimatt42: </p>
<hr />
<div>[[MDOS 6.50]] supports booting 'SYSTEM/SYS' from a Horizon or SNUG ramdisk at crubase >1400.<br />
<br />
== Limitations ==<br />
<br />
* The ramdisk disk must be assigned DSK6 during the boot process<br />
* Crubase >1400 should be used. (Others not tested)<br />
* Size of ramdisk is limited to 800k without extra hacking<br />
<br />
== Requirements ==<br />
<br />
* [[FORM123]] - https://atariage.com/forums/applications/core/interface/file/attachment.php?id=735056<br />
* [[MDOS 6.50]] SYSTEM/SYS - http://ftp.whtech.com/Geneve/GeneveOS_650_redist.dsk<br />
* The ability to boot into MDOS from some other device, such as a floppy on DSK1.<br />
* The system is not configured to boot something else before the [[Horizon Ramdisk]] see [[Geneve BOOT Order]]<br />
<br />
== Procedure ==<br />
<br />
# Set the CRUBASE of your Horizon ramdisk to >1400<br />
# Create a disk to boot the [[Geneve]] from that contains SYSTEM/SYS from [[MDOS 6.50]], [[CYA]], CYB, CYC, and [[FORM123]].<br />
# Boot to MDOS from you floppy on DSK1.<br />
# Load the ramdisk formatting tool: FORM123 ''Note: the FORM123 tool menus expect uppercase letters''<br />
# Select A "AUTOSCAN CRU LOCATIONS >1200 thru >1900".<br />
# Answer Y to "Format 16 Bit Ramdisk at CRU >1401 (Y/N)?"<br />
# Answer Y to "Set disk to boot MDOS >1400 (Y/N)?"<br />
# Answer Y to "Load SYSTEM/SYS From Disk to Ramdisk (Y/N)?"<br />
# Assuming you booted SYSTEM/SYS from DSK1, Answer 1 to "Select disk drive to load from(1-9)?"<br />
# Once it is finished copying - "Press Anykey To Continue" <br />
# Select X to exit back to MDOS.<br />
<br />
At this point you should be able to see the ramdisk and that it has SYSTEM/SYS on it. Perform DIR DSK8. You should see a listing with Volume name "RAMDSK1401", and a single file: "SYSTEM/SYS". The free space should be 2684 sectors. It should be able to boot, however it won't be able to find an AUTOEXEC on the ramdisk yet. <br />
<br />
# Verify that it can boot, press CTRL-SHIFT-SHIFT. <br />
<br />
It should load SYSTEM/SYS much faster than you would see from your floppy. When booting is complete, you will still be left at an A:\> prompt. That can be changed later.<br />
<br />
We need to now run CYA to configure the drive mapping during boot, so that it is DSK6.<br />
<br />
# give DSK8 a drive letter to make it easier to work with in CYA - assign E=DSK8: <br />
# Load MDOS into CYA for configuration: A:\CYA E:\SYSTEM"/"SYS<br />
# Select D for "(D)rive remap/assign"<br />
# Select R to map the 16-bit ramdisk into DSK6.<br />
# Select 6, then N<br />
# Press ESC to return up to previous menu.<br />
# Press ESC to return to the top menu.<br />
# Select S to "(S)ave SYSTEM/SYS"<br />
# Press ENTER to save to the ramdisk that we loaded it from. <br />
# Select Q to "(Q)uit CYA", and respond with Y<br />
<br />
Now, it should be able to boot off the Horizon ramdisk and find an AUTOEXEC on that ramdisk. So let's create an AUTOEXEC. E: should still be assigned to your ramdisk at this stage.<br />
<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ECHO RAMDISK<br />
# Press CTRL-Z to close the file.<br />
<br />
Now if press CTRL-SHIFT-SHIFT, it should boot from the ramdisk, and we should see 'RAMDISK' printed as evidence that it loaded the AUTOEXEC from the ramdisk. The ramdisk itself still doesn't have a drive letter assigned. We can correct that in our AUTOEXEC<br />
<br />
# Run: ASSIGN E=DSK6:<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ASSIGN E=DSK6:<br />
# Enter: E:<br />
# Enter: VER<br />
# Press CTRL-Z<br />
<br />
Now when you reboot, you should have the ramdisk available as drive letter E:, and you will be on drive E: by default.<br />
<br />
== Notes ==<br />
<br />
The [[MDOS 6.50]] redistribution disk image comes with [[FORM3MEG]], however the Geneve 0.98 and 1.00 boot roms are not capable of booting from the large volume it creates. It can be used to format an '8-bit' (256K) ramdisk that can boot, or '16-bit' larger volume that can be accessed after boot. There alleged to be an article in [[Micropendium]] describing how to boot from the fully allocated ramdisk. <br />
<br />
[[MDOS 6.70rc2]] will work with a 256K (8bit) ramdisk. With crubase >1400, the 8bit ramdisk device is mapped to DSK6 by default and allows MDOS to find the DSK6.AUTOEXEC. [[MDOS 6.70rc2]] does not have a supporting [[CYA]] program to alter assignements.</div>Jedimatt42http://www.ninerpedia.org/index.php?title=Booting_MDOS_from_Horizon_Ramdisk&diff=50320Booting MDOS from Horizon Ramdisk2020-05-31T16:24:26Z<p>Jedimatt42: </p>
<hr />
<div>[[MDOS 6.50]] supports booting 'SYSTEM/SYS' from a Horizon or SNUG ramdisk at crubase >1400.<br />
<br />
== Limitations ==<br />
<br />
* The ramdisk disk must be assigned DSK6 during the boot process<br />
* Crubase >1400 should be used. (Others not tested)<br />
* Size of ramdisk is limited to 800k without extra hacking<br />
<br />
== Requirements ==<br />
<br />
* [[FORM123]] - https://atariage.com/forums/applications/core/interface/file/attachment.php?id=735056<br />
* [[MDOS 6.50]] SYSTEM/SYS - http://ftp.whtech.com/Geneve/GeneveOS_650_redist.dsk<br />
* The ability to boot into MDOS from some other device, such as a floppy on DSK1.<br />
* The system is not configured to boot something else before the [[Horizon Ramdisk]] see [[Geneve BOOT Order]]<br />
<br />
== Procedure ==<br />
<br />
# Set the CRUBASE of your Horizon ramdisk to >1400<br />
# Create a disk to boot the [[Geneve]] from that contains SYSTEM/SYS from [[MDOS 6.50]], [[CYA]], CYB, CYC, and [[FORM123]].<br />
# Boot to MDOS from you floppy on DSK1.<br />
# Load the ramdisk formatting tool: FORM123 ''Note: the FORM123 tool menus expect uppercase letters''<br />
# Select A "AUTOSCAN CRU LOCATIONS >1200 thru >1900".<br />
# Answer Y to "Format 16 Bit Ramdisk at CRU >1401 (Y/N)?"<br />
# Answer Y to "Set disk to boot MDOS >1400 (Y/N)?"<br />
# Answer Y to "Load SYSTEM/SYS From Disk to Ramdisk (Y/N)?"<br />
# Assuming you booted SYSTEM/SYS from DSK1, Answer 1 to "Select disk drive to load from(1-9)?"<br />
# Once it is finished copying - "Press Anykey To Continue" <br />
# Select X to exit back to MDOS.<br />
<br />
At this point you should be able to see the ramdisk and that it has SYSTEM/SYS on it. Perform DIR DSK8. You should see a listing with Volume name "RAMDSK1401", and a single file: "SYSTEM/SYS". The free space should be 2684 sectors. It should be able to boot, however it won't be able to find an AUTOEXEC on the ramdisk yet. <br />
<br />
# Verify that it can boot, press CTRL-SHIFT-SHIFT. <br />
<br />
It should load SYSTEM/SYS much faster than you would see from your floppy. When booting is complete, you will still be left at an A:\> prompt. That can be changed later.<br />
<br />
We need to now run CYA to configure the drive mapping during boot, so that it is DSK6.<br />
<br />
# give DSK8 a drive letter to make it easier to work with in CYA - assign E=DSK8: <br />
# Load MDOS into CYA for configuration: A:\CYA E:\SYSTEM"/"SYS<br />
# Select D for "(D)rive remap/assign"<br />
# Select R to map the 16-bit ramdisk into DSK6.<br />
# Select 6, then N<br />
# Press ESC to return up to previous menu.<br />
# Press ESC to return to the top menu.<br />
# Select S to "(S)ave SYSTEM/SYS"<br />
# Press ENTER to save to the ramdisk that we loaded it from. <br />
# Select Q to "(Q)uit CYA", and respond with Y<br />
<br />
Now, it should be able to boot off the Horizon ramdisk and find an AUTOEXEC on that ramdisk. So let's create an AUTOEXEC. E: should still be assigned to your ramdisk at this stage.<br />
<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ECHO RAMDISK<br />
# Press CTRL-Z to close the file.<br />
<br />
Now if press CTRL-SHIFT-SHIFT, it should boot from the ramdisk, and we should see 'RAMDISK' printed as evidence that it loaded the AUTOEXEC from the ramdisk. The ramdisk itself still doesn't have a drive letter assigned. We can correct that in our AUTOEXEC<br />
<br />
# Run: ASSIGN E=DSK6:<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ASSIGN E=DSK6:<br />
# Enter: E:<br />
# Enter: VER<br />
# Press CTRL-Z<br />
<br />
Now when you reboot, you should have the ramdisk available as drive letter E:, and you will be on drive E: by default.<br />
<br />
== Notes ==<br />
<br />
The [[MDOS 6.50]] redistribution disk image comes with [[FORM3MEG]], however the Geneve 0.98 and 1.00 boot roms are not capable of loading from the large volume it creates. It can be used to format an '8-bit' (256K) ramdisk, but not the '16-bit' larger volume. <br />
<br />
[[MDOS 6.70rc2]] will work with a 256K (8bit) ramdisk. With crubase >1400, the 8bit ramdisk device is mapped to DSK6 by default and allows MDOS to find the DSK6.AUTOEXEC. [[MDOS 6.70rc2]] does not have a supporting [[CYA]] program to alter assignements.</div>Jedimatt42http://www.ninerpedia.org/index.php?title=Booting_MDOS_from_Horizon_Ramdisk&diff=50319Booting MDOS from Horizon Ramdisk2020-05-31T16:23:56Z<p>Jedimatt42: </p>
<hr />
<div>[[MDOS 6.50]] supports booting 'SYSTEM/SYS' from a Horizon or SNUG ramdisk at crubase >1400.<br />
<br />
== Limitations ==<br />
<br />
* The ramdisk disk must be assigned DSK6 during the boot process<br />
* Crubase >1400 should be used. (Others not tested)<br />
* Size of ramdisk is limited without extra hacking<br />
<br />
== Requirements ==<br />
<br />
* [[FORM123]] - https://atariage.com/forums/applications/core/interface/file/attachment.php?id=735056<br />
* [[MDOS 6.50]] SYSTEM/SYS - http://ftp.whtech.com/Geneve/GeneveOS_650_redist.dsk<br />
* The ability to boot into MDOS from some other device, such as a floppy on DSK1.<br />
* The system is not configured to boot something else before the [[Horizon Ramdisk]] see [[Geneve BOOT Order]]<br />
<br />
== Procedure ==<br />
<br />
# Set the CRUBASE of your Horizon ramdisk to >1400<br />
# Create a disk to boot the [[Geneve]] from that contains SYSTEM/SYS from [[MDOS 6.50]], [[CYA]], CYB, CYC, and [[FORM123]].<br />
# Boot to MDOS from you floppy on DSK1.<br />
# Load the ramdisk formatting tool: FORM123 ''Note: the FORM123 tool menus expect uppercase letters''<br />
# Select A "AUTOSCAN CRU LOCATIONS >1200 thru >1900".<br />
# Answer Y to "Format 16 Bit Ramdisk at CRU >1401 (Y/N)?"<br />
# Answer Y to "Set disk to boot MDOS >1400 (Y/N)?"<br />
# Answer Y to "Load SYSTEM/SYS From Disk to Ramdisk (Y/N)?"<br />
# Assuming you booted SYSTEM/SYS from DSK1, Answer 1 to "Select disk drive to load from(1-9)?"<br />
# Once it is finished copying - "Press Anykey To Continue" <br />
# Select X to exit back to MDOS.<br />
<br />
At this point you should be able to see the ramdisk and that it has SYSTEM/SYS on it. Perform DIR DSK8. You should see a listing with Volume name "RAMDSK1401", and a single file: "SYSTEM/SYS". The free space should be 2684 sectors. It should be able to boot, however it won't be able to find an AUTOEXEC on the ramdisk yet. <br />
<br />
# Verify that it can boot, press CTRL-SHIFT-SHIFT. <br />
<br />
It should load SYSTEM/SYS much faster than you would see from your floppy. When booting is complete, you will still be left at an A:\> prompt. That can be changed later.<br />
<br />
We need to now run CYA to configure the drive mapping during boot, so that it is DSK6.<br />
<br />
# give DSK8 a drive letter to make it easier to work with in CYA - assign E=DSK8: <br />
# Load MDOS into CYA for configuration: A:\CYA E:\SYSTEM"/"SYS<br />
# Select D for "(D)rive remap/assign"<br />
# Select R to map the 16-bit ramdisk into DSK6.<br />
# Select 6, then N<br />
# Press ESC to return up to previous menu.<br />
# Press ESC to return to the top menu.<br />
# Select S to "(S)ave SYSTEM/SYS"<br />
# Press ENTER to save to the ramdisk that we loaded it from. <br />
# Select Q to "(Q)uit CYA", and respond with Y<br />
<br />
Now, it should be able to boot off the Horizon ramdisk and find an AUTOEXEC on that ramdisk. So let's create an AUTOEXEC. E: should still be assigned to your ramdisk at this stage.<br />
<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ECHO RAMDISK<br />
# Press CTRL-Z to close the file.<br />
<br />
Now if press CTRL-SHIFT-SHIFT, it should boot from the ramdisk, and we should see 'RAMDISK' printed as evidence that it loaded the AUTOEXEC from the ramdisk. The ramdisk itself still doesn't have a drive letter assigned. We can correct that in our AUTOEXEC<br />
<br />
# Run: ASSIGN E=DSK6:<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ASSIGN E=DSK6:<br />
# Enter: E:<br />
# Enter: VER<br />
# Press CTRL-Z<br />
<br />
Now when you reboot, you should have the ramdisk available as drive letter E:, and you will be on drive E: by default.<br />
<br />
== Notes ==<br />
<br />
The [[MDOS 6.50]] redistribution disk image comes with [[FORM3MEG]], however the Geneve 0.98 and 1.00 boot roms are not capable of loading from the large volume it creates. It can be used to format an '8-bit' (256K) ramdisk, but not the '16-bit' larger volume. <br />
<br />
[[MDOS 6.70rc2]] will work with a 256K (8bit) ramdisk. With crubase >1400, the 8bit ramdisk device is mapped to DSK6 by default and allows MDOS to find the DSK6.AUTOEXEC. [[MDOS 6.70rc2]] does not have a supporting [[CYA]] program to alter assignements.</div>Jedimatt42http://www.ninerpedia.org/index.php?title=Booting_MDOS_from_Horizon_Ramdisk&diff=50318Booting MDOS from Horizon Ramdisk2020-05-31T16:20:49Z<p>Jedimatt42: Created page with "MDOS 6.50 supports booting 'SYSTEM/SYS' from a Horizon or SNUG ramdisk at crubase >1400. == Limitations == * The disk must be assigned DSK6 during the boot process * Cru..."</p>
<hr />
<div>[[MDOS 6.50]] supports booting 'SYSTEM/SYS' from a Horizon or SNUG ramdisk at crubase >1400.<br />
<br />
== Limitations ==<br />
<br />
* The disk must be assigned DSK6 during the boot process<br />
* Crubase >1400 should be used. (Others not tested)<br />
* Size of ramdisk is limited without extra hacking<br />
<br />
== Requirements ==<br />
<br />
* [[FORM123]] - https://atariage.com/forums/applications/core/interface/file/attachment.php?id=735056<br />
* [[MDOS 6.50]] SYSTEM/SYS - http://ftp.whtech.com/Geneve/GeneveOS_650_redist.dsk<br />
* The ability to boot into MDOS from some other device, such as a floppy on DSK1.<br />
* The system is not configured to boot something else before the [[Horizon Ramdisk]] see [[Geneve BOOT Order]]<br />
<br />
== Procedure ==<br />
<br />
# Set the CRUBASE of your Horizon ramdisk to >1400<br />
# Create a disk to boot the [[Geneve]] from that contains SYSTEM/SYS from [[MDOS 6.50]], [[CYA]], CYB, CYC, and [[FORM123]].<br />
# Boot to MDOS from you floppy on DSK1.<br />
# Load the ramdisk formatting tool: FORM123 ''Note: the FORM123 tool menus expect uppercase letters''<br />
# Select A "AUTOSCAN CRU LOCATIONS >1200 thru >1900".<br />
# Answer Y to "Format 16 Bit Ramdisk at CRU >1401 (Y/N)?"<br />
# Answer Y to "Set disk to boot MDOS >1400 (Y/N)?"<br />
# Answer Y to "Load SYSTEM/SYS From Disk to Ramdisk (Y/N)?"<br />
# Assuming you booted SYSTEM/SYS from DSK1, Answer 1 to "Select disk drive to load from(1-9)?"<br />
# Once it is finished copying - "Press Anykey To Continue" <br />
# Select X to exit back to MDOS.<br />
<br />
At this point you should be able to see the ramdisk and that it has SYSTEM/SYS on it. Perform DIR DSK8. You should see a listing with Volume name "RAMDSK1401", and a single file: "SYSTEM/SYS". The free space should be 2684 sectors. It should be able to boot, however it won't be able to find an AUTOEXEC on the ramdisk yet. <br />
<br />
# Verify that it can boot, press CTRL-SHIFT-SHIFT. <br />
<br />
It should load SYSTEM/SYS much faster than you would see from your floppy. When booting is complete, you will still be left at an A:\> prompt. That can be changed later.<br />
<br />
We need to now run CYA to configure the drive mapping during boot, so that it is DSK6.<br />
<br />
# give DSK8 a drive letter to make it easier to work with in CYA - assign E=DSK8: <br />
# Load MDOS into CYA for configuration: A:\CYA E:\SYSTEM"/"SYS<br />
# Select D for "(D)rive remap/assign"<br />
# Select R to map the 16-bit ramdisk into DSK6.<br />
# Select 6, then N<br />
# Press ESC to return up to previous menu.<br />
# Press ESC to return to the top menu.<br />
# Select S to "(S)ave SYSTEM/SYS"<br />
# Press ENTER to save to the ramdisk that we loaded it from. <br />
# Select Q to "(Q)uit CYA", and respond with Y<br />
<br />
Now, it should be able to boot off the Horizon ramdisk and find an AUTOEXEC on that ramdisk. So let's create an AUTOEXEC. E: should still be assigned to your ramdisk at this stage.<br />
<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ECHO RAMDISK<br />
# Press CTRL-Z to close the file.<br />
<br />
Now if press CTRL-SHIFT-SHIFT, it should boot from the ramdisk, and we should see 'RAMDISK' printed as evidence that it loaded the AUTOEXEC from the ramdisk. The ramdisk itself still doesn't have a drive letter assigned. We can correct that in our AUTOEXEC<br />
<br />
# Run: ASSIGN E=DSK6:<br />
# Run: COPY CON E:\AUTOEXEC<br />
# Enter: ASSIGN E=DSK6:<br />
# Enter: E:<br />
# Enter: VER<br />
# Press CTRL-Z<br />
<br />
Now when you reboot, you should have the ramdisk available as drive letter E:, and you will be on drive E: by default.<br />
<br />
== Notes ==<br />
<br />
The [[MDOS 6.50]] redistribution disk image comes with [[FORM3MEG]], however the Geneve 0.98 and 1.00 boot roms are not capable of loading from the large volume it creates. It can be used to format an '8-bit' (256K) ramdisk, but not the '16-bit' larger volume. <br />
<br />
[[MDOS 6.70rc2]] will work with a 256K (8bit) ramdisk. With crubase >1400, the 8bit ramdisk device is mapped to DSK6 by default and allows MDOS to find the DSK6.AUTOEXEC. [[MDOS 6.70rc2]] does not have a supporting [[CYA]] program to alter assignements.</div>Jedimatt42http://www.ninerpedia.org/index.php?title=Memory_Expansion_Cards&diff=50229Memory Expansion Cards2019-04-28T18:43:54Z<p>Jedimatt42: /* clarification of testing Thiery's board design */</p>
<hr />
<div>The TI console has only 256 bytes of 16-bit CPU RAM directly connected to the address and data buses. This small amount of RAM provides register space to the CPU and is used to support the GPL interpreter when executing its code from a specialized type of memory called Graphics Read Only Memory (GROM). GROMs are typically 6 KB in size and have their own auto-incrementing address bus. Instructions are placed on the data bus and read by the CPU. Each GROM chip is accessed as a parallel device. User programs - usually BASIC programs - have to be stored in the video RAM. The strategy was as follows:<br />
<br />
* For normal BASIC programming, only simple video functions are necessary. So there is a (comparable) lot of free space which can be used for user programs. <br />
* If more complex video functions are necessary, the programs may be stored in GROMs or ROMs in cartridges.<br />
* If people still want to write own programs and have nice video output, they should purchase a memory expansion.<br />
<br />
<br />
== Original TI Memory Expansion ==<br />
<br />
[[Image:MemExp800.jpg|200px|left]]<br />
<br />
The picture shows the 32K Memory Expansion card, which placed RAM in memory locations >2000<sup>1</sup> - >3FFF and >A000 - >FFFF. Using this RAM opened up the world of assembly programming on the TI, and from there, other [[Programming languages|languages]] became available over time (like FORTH, PASCAL, C). In addition, independent software authors could finally create complex programs without the need to burn them into cartridges.<br />
<br />
<sup>1</sup><small>Hexadecimal notation in the TI world was marked with a greater-than sign, i.e. >2000 is 0x2000.</small><br />
<br />
<div style="clear:both"></div><br />
<br />
== 128K SuperRAM Memory Expansion ==<br />
<br />
This card was considered vapor-ware for many years. At least one survived, however, though it was only partially assembled.<br />
<br />
== GRAM Card ==<br />
<br />
This card was developed at the TI laboratory in Almelo, Holland, apparently as an alternative to the external GROM device developed in the US. It was completely unknown to users until after TI withdrew from the home computer market and served as a proof-of-concept template from which the Mechatronics GRAM Karte was eventually developed. Only four examples of the card survive, all of them rescued from a dumpster by a sharp-eyed TI enthusiast who once worked at the Almelo labs.<br />
<br />
The card uses the same GRAM header format as the Mechatronics GRAM Karte. It has a special cartridge board attached to a cable on the card which must be inserted into the computer's cartridge port to make the programs stored in the card available to the computer. They will then appear normally on the menu screen and start when selected. Unlike the Miller's Graphics GRAM Kracker, this card does not simulate GROMs 0, 1, and 2. Only the cartridge port GROMs and ROMs are simulated.<br />
<br />
== Atronics 32K Memory Expansion ==<br />
<br />
TODO<br />
<br />
== Captain's Wheel 32K Memory Expansion ==<br />
<br />
This rare card duplicated the functionality of the TI 32K Memory Expansion card. It did not come with a clam shell case. Only a dozen or so of these cards are known to survive.<br />
<br />
== CorComp 32K Memory Interface ==<br />
<br />
TODO<br />
<br />
== CorComp 512K Memory Card ==<br />
<br />
TODO<br />
<br />
== DataBioTics Grand RAM ==<br />
<br />
TODO<br />
<br />
== Foundation 32K/128K Memory Card ==<br />
<br />
This card duplicated the functionality of the TI 32K Memory Expansion card in its basic configuration, but added a 96K RAM Disk when purchased in the expanded, 128K version. The larger card required a DSR to utilize it to its fullest extent, which was sold initially as an option but was automatically included on later sales. Several utility programs were written to take advantage of the card's additional storage capabilities, including Mass Copy by Steve Lawless.<br />
<br />
Later users devised a modified DSR to allow it to use the Myarc 128K OS--and Myarc Extended BASIC 2.11. Similar modifications exist to allow the card to be expanded to 512K.<br />
<br />
== Horizon Ramdisk 1000/2000/3000/4000 Series ==<br />
<br />
TODO<br />
<br />
== Horizon P-GRAM Card ==<br />
<br />
TODO<br />
<br />
== ICS 32K Memory Expansion ==<br />
<br />
This rare card duplicated the functionality of the TI 32K Memory Expansion card. It did not come with a clam shell case. Only a dozen or so of these cards are known to survive.<br />
<br />
== Mechatronics GRAM Karte ==<br />
<br />
TODO<br />
<br />
== Morning Star 128K Memory Expansion ==<br />
<br />
This card was intended to provide additional memory to the TI-99/4A, in a fashion similar to the 128K Memory Expansion from Foundation. It never lived up to this promise because the DSR for the card was never released. It existed, but the programmer refused to turn it over to Morning Star until he was paid for his work. The card only works as a standard 32K Memory Expansion when inserted into the PEB as a result of the missing DSR. Very few of these cards were sold, with less than 20 known to exist today.<br />
<br />
== Myarc 32K/128K/512K Memory Expansion ==<br />
<br />
TODO<br />
<br />
== SNUG High-Speed GPL (HSGPL) Card ==<br />
<br />
Please refer to main article on the [[HSGPL]] card<br />
<br />
== SNUG High-Speed RAM Disk-16 (HRD-16) ==<br />
Please refer to [[SNUG#HRD 16 | SNUG High Speed Ram Disk]]<br />
<br />
== South-West 99ers SAMS Memory Card ==<br />
<br />
The earliest versions of this card were developed for [[Asgard Software]], and were called the Asgard Memory System. Only a small run of the Asgard card was produced, with most of them going to developers in exchange for promises to write software that used the card. The South-West 99ers carried the design much further, increasing the possible memory size from 128K to 256K and eventually up to 1MB. A full suite of development software that uses the capabilities of the card was developed to allow programmers to easily harness it, but it (hardware and software) reached production readiness too late in the life cycle of the TI-99/4A to get widespread support. This is unfortunate, as it is easily one of the ten best expansion items ever developed for the machine. The card is in production again as a kit (summer 2007), giving the possibility of exciting new software for it if it gains sufficient acceptance within the TI community.<br />
<br />
[[SuperAMS]]<br />
<br />
== Do It Yourself 32k Memory ==<br />
<br />
There are several available designs for internal memory expansion inside a TI-99/4A console. <br />
<br />
* [http://www.mainbyte.com/ti99/32K16/32k16.html 16 bit ram on an internal board]<br />
* [http://atariage.com/forums/topic/206520-internal-16-bit-32k-upgrade/?p=2705086 Anders Persson 16 bit 64k design]<br />
* [https://www.harmlesslion.com/text/TI%2032k%20Mod.pdf 2-chip 8 bit internal 32k]<br />
<br />
Thierry Nouspikel details a proposed schematic for a PEB expansion card (labeled as untested). The Jedimatt42 sideport prototype design confirmed 95% of this circuit, except control of RDBENA (the flex cable bus transceiver). The sideport expansion was then refined to remove some of the bus buffers in the final version. <br />
<br />
* [http://www.nouspikel.com/ti99/titechpages.htm Theiry Nouspikel PEB card design]<br />
* [https://www.jedimatt42.com/ti32kmem.html 8-bit 32k sideport] <br />
<br />
[[Category:Hardware]]<br />
[[Category:Expansion]]</div>Jedimatt42http://www.ninerpedia.org/index.php?title=Memory_Expansion_Cards&diff=50228Memory Expansion Cards2019-04-28T17:48:42Z<p>Jedimatt42: </p>
<hr />
<div>The TI console has only 256 bytes of 16-bit CPU RAM directly connected to the address and data buses. This small amount of RAM provides register space to the CPU and is used to support the GPL interpreter when executing its code from a specialized type of memory called Graphics Read Only Memory (GROM). GROMs are typically 6 KB in size and have their own auto-incrementing address bus. Instructions are placed on the data bus and read by the CPU. Each GROM chip is accessed as a parallel device. User programs - usually BASIC programs - have to be stored in the video RAM. The strategy was as follows:<br />
<br />
* For normal BASIC programming, only simple video functions are necessary. So there is a (comparable) lot of free space which can be used for user programs. <br />
* If more complex video functions are necessary, the programs may be stored in GROMs or ROMs in cartridges.<br />
* If people still want to write own programs and have nice video output, they should purchase a memory expansion.<br />
<br />
<br />
== Original TI Memory Expansion ==<br />
<br />
[[Image:MemExp800.jpg|200px|left]]<br />
<br />
The picture shows the 32K Memory Expansion card, which placed RAM in memory locations >2000<sup>1</sup> - >3FFF and >A000 - >FFFF. Using this RAM opened up the world of assembly programming on the TI, and from there, other [[Programming languages|languages]] became available over time (like FORTH, PASCAL, C). In addition, independent software authors could finally create complex programs without the need to burn them into cartridges.<br />
<br />
<sup>1</sup><small>Hexadecimal notation in the TI world was marked with a greater-than sign, i.e. >2000 is 0x2000.</small><br />
<br />
<div style="clear:both"></div><br />
<br />
== 128K SuperRAM Memory Expansion ==<br />
<br />
This card was considered vapor-ware for many years. At least one survived, however, though it was only partially assembled.<br />
<br />
== GRAM Card ==<br />
<br />
This card was developed at the TI laboratory in Almelo, Holland, apparently as an alternative to the external GROM device developed in the US. It was completely unknown to users until after TI withdrew from the home computer market and served as a proof-of-concept template from which the Mechatronics GRAM Karte was eventually developed. Only four examples of the card survive, all of them rescued from a dumpster by a sharp-eyed TI enthusiast who once worked at the Almelo labs.<br />
<br />
The card uses the same GRAM header format as the Mechatronics GRAM Karte. It has a special cartridge board attached to a cable on the card which must be inserted into the computer's cartridge port to make the programs stored in the card available to the computer. They will then appear normally on the menu screen and start when selected. Unlike the Miller's Graphics GRAM Kracker, this card does not simulate GROMs 0, 1, and 2. Only the cartridge port GROMs and ROMs are simulated.<br />
<br />
== Atronics 32K Memory Expansion ==<br />
<br />
TODO<br />
<br />
== Captain's Wheel 32K Memory Expansion ==<br />
<br />
This rare card duplicated the functionality of the TI 32K Memory Expansion card. It did not come with a clam shell case. Only a dozen or so of these cards are known to survive.<br />
<br />
== CorComp 32K Memory Interface ==<br />
<br />
TODO<br />
<br />
== CorComp 512K Memory Card ==<br />
<br />
TODO<br />
<br />
== DataBioTics Grand RAM ==<br />
<br />
TODO<br />
<br />
== Foundation 32K/128K Memory Card ==<br />
<br />
This card duplicated the functionality of the TI 32K Memory Expansion card in its basic configuration, but added a 96K RAM Disk when purchased in the expanded, 128K version. The larger card required a DSR to utilize it to its fullest extent, which was sold initially as an option but was automatically included on later sales. Several utility programs were written to take advantage of the card's additional storage capabilities, including Mass Copy by Steve Lawless.<br />
<br />
Later users devised a modified DSR to allow it to use the Myarc 128K OS--and Myarc Extended BASIC 2.11. Similar modifications exist to allow the card to be expanded to 512K.<br />
<br />
== Horizon Ramdisk 1000/2000/3000/4000 Series ==<br />
<br />
TODO<br />
<br />
== Horizon P-GRAM Card ==<br />
<br />
TODO<br />
<br />
== ICS 32K Memory Expansion ==<br />
<br />
This rare card duplicated the functionality of the TI 32K Memory Expansion card. It did not come with a clam shell case. Only a dozen or so of these cards are known to survive.<br />
<br />
== Mechatronics GRAM Karte ==<br />
<br />
TODO<br />
<br />
== Morning Star 128K Memory Expansion ==<br />
<br />
This card was intended to provide additional memory to the TI-99/4A, in a fashion similar to the 128K Memory Expansion from Foundation. It never lived up to this promise because the DSR for the card was never released. It existed, but the programmer refused to turn it over to Morning Star until he was paid for his work. The card only works as a standard 32K Memory Expansion when inserted into the PEB as a result of the missing DSR. Very few of these cards were sold, with less than 20 known to exist today.<br />
<br />
== Myarc 32K/128K/512K Memory Expansion ==<br />
<br />
TODO<br />
<br />
== SNUG High-Speed GPL (HSGPL) Card ==<br />
<br />
Please refer to main article on the [[HSGPL]] card<br />
<br />
== SNUG High-Speed RAM Disk-16 (HRD-16) ==<br />
Please refer to [[SNUG#HRD 16 | SNUG High Speed Ram Disk]]<br />
<br />
== South-West 99ers SAMS Memory Card ==<br />
<br />
The earliest versions of this card were developed for [[Asgard Software]], and were called the Asgard Memory System. Only a small run of the Asgard card was produced, with most of them going to developers in exchange for promises to write software that used the card. The South-West 99ers carried the design much further, increasing the possible memory size from 128K to 256K and eventually up to 1MB. A full suite of development software that uses the capabilities of the card was developed to allow programmers to easily harness it, but it (hardware and software) reached production readiness too late in the life cycle of the TI-99/4A to get widespread support. This is unfortunate, as it is easily one of the ten best expansion items ever developed for the machine. The card is in production again as a kit (summer 2007), giving the possibility of exciting new software for it if it gains sufficient acceptance within the TI community.<br />
<br />
[[SuperAMS]]<br />
<br />
== Do It Yourself 32k Memory ==<br />
<br />
There are several available designs for internal memory expansion inside a TI-99/4A console. <br />
<br />
* [http://www.mainbyte.com/ti99/32K16/32k16.html 16 bit ram on an internal board]<br />
* [http://atariage.com/forums/topic/206520-internal-16-bit-32k-upgrade/?p=2705086 Anders Persson 16 bit 64k design]<br />
* [https://www.harmlesslion.com/text/TI%2032k%20Mod.pdf 2-chip 8 bit internal 32k]<br />
<br />
Thiery Nouspikel details a proposed schematic for a PEB expansion card (labeled as untested). The Jedimatt42 sideport prototype design confirmed 95% of this circuit, before refining to remove some of the bus buffers in the final version. <br />
<br />
* [http://www.nouspikel.com/ti99/titechpages.htm Theiry Nouspikel PEB card design]<br />
* [https://www.jedimatt42.com/ti32kmem.html 8-bit 32k sideport] <br />
<br />
[[Category:Hardware]]<br />
[[Category:Expansion]]</div>Jedimatt42http://www.ninerpedia.org/index.php?title=Geneve_9640&diff=50227Geneve 96402019-04-28T16:55:40Z<p>Jedimatt42: /* MDOS 2.50 and greater can be run without this mod, if the user has 1 of 2 available external memory expansions. */</p>
<hr />
<div>In 1987, [[Myarc]] - already known in the TI community for several peripheral expansion cards - launched the '''Geneve 9640''', a complete computer on a card, intended to replace the original TI console.<br />
<br />
[[Image:Geneve_expansion_card.jpg|200px|left]]<br />
<br />
Some rumours tell that the name Geneve was derived from a picture of Geneva (French: Génève) seen by one of the responsible designers. The addition 9640 should be read "9-640":<br />
<br />
[[Image:Geneve_pcb.jpg|250px|right]]<br />
<br />
* Originally, the name should refer to TI-99, but Myarc did not get the permission to create such a similar name. The single "9" shall keep a little bit of reference to the roots, the [[TI-99/4A]].<br />
* The new computer was designed to have a main memory of 640 KiB (main+video), comparable to the RAM size of common PCs at that time.<br />
<br />
As the TI console is not required anymore, the flex cable interface becomes obsolete. The long flex cable also showed signs of wear after years, so dropping the cable removed yet another source of instabilities.<sup>1</sup><br />
<br />
<sup>1</sup><small>At least for my system.</small><br />
<br />
== Features ==<br />
<br />
[[Image:Geneve_boot_screenshot_09.png|thumb|right|The Geneve Boot Screen (original)]]<br />
As a computer of 1987, the Geneve shows an impressive performance on many areas, getting close to common PCs at that time:<br />
<br />
* PC-XT keyboard interface<br />
* Three-button mouse<br />
* 512 KiB System RAM (expandable to 2 MiB)<br />
* 128 KiB Video RAM<br />
* Compatible Video Controller, introducing new resolutions<br />
* Real-time clock<br />
* TMS 9995 processor on 12 MHz speed<br />
<br />
Most important, the Geneve uses the TMS 9995 processor which is compatible to the TMS 9900 from the TI-99/4A, adding four more instructions. The video controller is a MSX 9938 which is also compatible to the TMS 9918 family. In order to increase compatibility, the Geneve offered a "GPL Mode" which reorganized the address layout to the TI-99/4A style. In that way, nearly all TI programs can run on the Geneve without any modification. Cartridges have to be copied to disk as the Geneve does not offer a cartridge slot.<br />
<br />
== Operating system ==<br />
<br />
The Geneve has a built-in boot ROM, but this only provides a simple loader for a disk operating system, which, by some similarities to other known operating systems, was named '''MDOS''' (Myarc Disk Operating System). <br />
<br />
MDOS is currently still maintained and under ongoing development. The latest version is 6.50 and has been released as freely distributable. With this release, MDOS has been relabeled as '''Geneve OS'''. You can download a [[Geneve OS|disk image]] for use in the MESS emulator.<br />
<br />
== Modifications ==<br />
<br />
=== Boot ROM ===<br />
[[Image:Geneve_boot_screenshot_10.png|thumb|left|The Geneve Boot Screen (EPROM version 1.0)]]<br />
There has also been an update to the Geneve boot ROM which allows to choose the boot device. The original boot ROM could only boot from a floppy disk in drive one, or from a hard drive, but this hard drive must be addressed as HDS1. Other drives, especially SCSI drives, are not able to boot with the original ROM.<br />
<br />
<div style="clear:both"></div><br />
<br />
=== Onboard Memory Expansion ===<br />
<br />
[[Image:Geneve_mexp.jpg|200px|right]]<br />
<br />
Another popular extension is the CPU memory upgrade to 576 KiB. This modification is mandatory if MDOS 2.50 and above shall be used without an additional memory expansion board. The multi-layered printed board layout makes such modifications pretty difficult (if possible at all), but in this case it is only required to solder another SRAM piggy-back onto the existing RAM circuit. One of the select lines must be connected to the Gate array. Here are the detailed [[Geneve CPU Memory Upgrade | instructions]].<br />
<br />
<br />
<div style="clear:both"></div><br />
<br />
=== GenMod ===<br />
<br />
The GenMod modification is a significant enhancement of the Geneve board when used together with a MEMEX memory expansion card: <br />
<br />
* Full usage of 2 MiB address space.<br />
* Zero wait state for external memory.<br />
<br />
This requires a set of modifications to the Geneve board.<br />
<br />
[[Image:Genmod_up.jpg|200px|left]]<br />
<br />
[[Image:Genmod_down.jpg|200px|right]]<br />
<br />
<div style="clear:both"></div><br />
<br />
== Tips ==<br />
<br />
As the circuit board of the Geneve extends outside of the Peripheral Extension Box, there is some chance that the box slot gets in contact with the board, causing a short circuit. It is a very good idea to protect the portion of the circuit card that extends outside the PEB with electrical tape to shield it from possible damage by the fingers to either side of the PEB slots.<br />
<br />
== Acceptance ==<br />
<br />
While the Geneve, with its remarkable new features and much higher speed, gained a lot of attention in some parts of the TI community, other TI users were somewhat less impressed. This was probably due to these reasons:<br />
<br />
* Earlier products from Myarc suffered from stability problems. There was not much confidence that this should have changed for this complex new project.<br />
* Myarc decided for a high integration on the circuit board which required multi-layer boards. As a pretty large part of the community is dedicated to hardware projects on the TI, the new Geneve makes modifications hard or even impossible.<br />
* Not only the hardware but specifically the implementation of DSRs showed that Myarc programmers did not pay enough attention to standards within the TI architecture. For example, instead of using the standard way of inspecting the peripheral card DSRs for devices, the Myarc DOS for the Geneve included these devices in the code, leaving no way to include new peripherals anymore.<br />
<br />
Therefore, the acceptance of the Geneve depends much on the area of interest of the user: While hardware-related projects mostly keep away from the new computer, software authors welcomed the new features, and quite a lot of programs have been written. The Myarc DOS (MDOS) is still developing.<br />
<br />
== Technical details ==<br />
<br />
* [[Geneve paged memory organization|Paged memory organization]] <br />
* [[Geneve CRU definitions|CRU definitions]]<br />
* [[Geneve GPL Interpreter]]<br />
* [[Geneve wait state generation|Wait state generation]]<br />
* [[Geneve External bus definition | External bus definition]]<br />
* [[Geneve drive remapping | Drive remapping]]<br />
<br />
[[Category:Hardware]]<br />
[[Category:Geneve]]</div>Jedimatt42http://www.ninerpedia.org/index.php?title=TIPI&diff=50226TIPI2019-04-25T02:01:30Z<p>Jedimatt42: </p>
<hr />
<div>Open source hardware and software to connect a Raspberry Pi.<br />
* File server<br />
* Network server<br />
* Mouse interface<br />
<br />
[https://github.com/jedimatt42/tipi/wiki Project Documentation]<br />
<br />
[[Category:Hardware]]</div>Jedimatt42