Jump to content

Photo

indus cpm with altirra 3.1


5 replies to this topic

#1 funkheld OFFLINE  

funkheld

    Moonsweeper

  • 370 posts

Posted Thu May 17, 2018 11:51 AM

hello, how is the indus cp/m started with altirra 3.1?
 
 
 disk 1 = Indus RAM Charger 40-80 Terminal.atr
 disk 2 = Indus RAM Charger CPM Boot.atr
 
 startet disk 1 with "E" ist character 80/40
 starting ok.
 
 then rotate down disk
 
 
 system/console switches : indus GT : Boot CP/M
 is not active (gray)
 
 who can set the start order and which disk to use?
 
 thanks

Edited by funkheld, Thu May 17, 2018 11:52 AM.


#2 phaeron OFFLINE  

phaeron

    River Patroller

  • 2,629 posts
  • Location:Bay Area, CA, USA

Posted Thu May 17, 2018 10:02 PM

First, the CP/M disk on that website is corrupted because the ATR file format can't store the boot sectors properly. You need an XFD image. I posted a fixed one in this post: http://atariage.com/...ased/?p=3632276

 

Second, you need to configure Altirra to emulate the full Indus GT disk drive, including its Z80 CPU. If that menu items is grayed out (disabled), things aren't set up properly. To do this, you will need an Indus GT firmware ROM image, which doesn't come with the emulator. Do not use the mislabeled "1.4" firmware that's floating around, that's actually an old 1.1 firmware that is buggy compared to 1.2. Latest 3.10-test will detect the Indus GT ROMs when you do Scan on a folder in Firmware Manager.

 

Assuming you have that, the steps are as follows:

  • System > Configure System > Devices or System > Devices, depending on whether you are using 3.00 or 3.10-test
  • Add > Disk Drives (full emulation) > Indus GT (full emulation)
  • System > Configure System > Firmware > Firmware Manager (3.10-test) or System > Firmware > Firmware Manager (3.00), Add, select Indus GT ROM image, set Type: Indus GT Drive Firmware.
  • (3.00 only) Make sure System > Disk > Accurate Sector Timing is unchecked, or the boot will be very slow.
  • (3.10-test only) System > Disk Drives, select the right arrow flyout by the Indus CP/M disk, select Change Interleave > 1:1 so the disk loads at the proper speed.
  • Then attempt the boot procedure you previously tried.

 



#3 sup8pdct OFFLINE  

sup8pdct

    Dragonstomper

  • 882 posts
  • Location:australia

Posted Fri May 18, 2018 2:29 AM

I thought the way indus booted cpm was to press 2 buttons on the front of the drive it self. Indus needs ramcharger. is that emulated?

 

James



#4 funkheld OFFLINE  

funkheld

    Moonsweeper

  • Topic Starter
  • 370 posts

Posted Fri May 18, 2018 9:03 AM

thanks for very info.

 

greeting



#5 phaeron OFFLINE  

phaeron

    River Patroller

  • 2,629 posts
  • Location:Bay Area, CA, USA

Posted Fri May 18, 2018 9:55 PM

I thought the way indus booted cpm was to press 2 buttons on the front of the drive it self. Indus needs ramcharger. is that emulated?


Yes, the RAMCharger is emulated.

Booting Indus CP/M on the drive does indeed involve pressing two buttons, specifically Drive Type + Error. This is impossible through the emulator interface, though, so another virtual button is exposed to do the two-press for you. This is done after booting the terminal software on the Atari.



#6 funkheld OFFLINE  

funkheld

    Moonsweeper

  • Topic Starter
  • 370 posts

Posted Sat May 19, 2018 4:55 AM

why is indus12.zip ?

 

why cp/m 2.2 disk ?

 

greeting






0 user(s) are browsing this forum

0 members, 0 guests, 0 anonymous users