Jump to content
IGNORED

On DOS & how to start executables?


jowi

Recommended Posts

Now i've never had the pleasure back in the day to work with floppies and Atari dos, so i'm trying to catch up... so this question is probably very stupid :)

 

I've downloaded the Atari Assembler Editor with DOS 2.0S.atr from https://atariwiki.org/wiki/Wiki.jsp?page=Atari%20Assembler%20Editor, and set it as disk 1 in Respeqt, and boot the 600XL. The machine boots, and the disk is loaded, and Dos 2.0 starts running. So far so good :)

 

If i list the contents of the disk with command A, it shows 2 .com files besides the dos.sys, dup.sys and autorun,sys: ASMCARA.COM and ASMCARB.COM, me thinks these are the A and B revisions of the Editor/Assembler mentioned on the wiki.

Now, how do i start these? I've tried using the L command, but if i load ASMCARB.COM, it just shows a garbled screen and hangs...

 

How does one start a .COM or an .XEX etc from DOS 2.0/2.5?

Or do you need to go to basic and start things from there?

Edited by jowi
Link to comment
Share on other sites

Now i've never had the pleasure back in the day to work with floppies and Atari dos, so i'm trying to catch up... so this question is probably very stupid :)

 

I've downloaded the Atari Assembler Editor with DOS 2.0S.atr from https://atariwiki.org/wiki/Wiki.jsp?page=Atari%20Assembler%20Editor, and set it as disk 1 in Respeqt, and boot the 600XL. The machine boots, and the disk is loaded, and Dos 2.0 starts running. So far so good :)

 

If i list the contents of the disk with command A, it shows 2 .com files besides the dos.sys, dup.sys and autorun,sys: ASMCARA.COM and ASMCARB.COM, me thinks these are the A and B revisions of the Editor/Assembler mentioned on the wiki.

Now, how do i start these? I've tried using the L command, but if i load ASMCARB.COM, it just shows a garbled screen and hangs...

 

How does one start a .COM or an .XEX etc from DOS 2.0/2.5?

Or do you need to go to basic and start things from there?

the L (Load Binary) should do the trick. Are you perhaps booting the machine with BASIC enabled?

Link to comment
Share on other sites

If i hold OPTION to omit Basic, the disk gets loaded and by the looks of it, starts one of the assemblers, because the screen gets garbled immediately. If i boot with Basic enabled, DOS gets started, and if i use L to start one of the assemblers, the screen gets garbled again...

Link to comment
Share on other sites

Programmed in 1980, so maybe it requires OLD-OS (OS-A or OS-B) ?!?

If so, first load the translator disk or something similar with OS-A or OS-B and Basic off on your XL/XE, then load one of the Assembler Editor versions...

Good call. I switched to OS/A in Altirra, and it boots right into the ASM/ED (basic disabled, autorun.sys loads).

Link to comment
Share on other sites

Programmed in 1980, so maybe it requires OLD-OS (OS-A or OS-B) ?!?

If so, first load the translator disk or something similar with OS-A or OS-B and Basic off on your XL/XE, then load one of the Assembler Editor versions...

Thanks, but i’m not sure i understand correctly; why would they put dos 2.0 together with the assembler, if you need a second disk with another os? I would have thought the whole idea for this was to have some sort of integrated environment.

 

For my “real” atari i’m using the actual cartridge together with a dos 2.5 floppy in aspeqt.

This 2.0 disk was for using on altirra emulator, so how do i fix this for altirra? do i need a os/a rom to base my emulated atari on?

Link to comment
Share on other sites

I do have a 600XL with 64K.

 

If i boot the dos/edasm disk in the emulator, it works fine now (altirra configured as a 64K XL machine, Basic disabled on boot). It starts right into the assembler.

If i boot the disk on the actual hardware (600XL/64K) with OPTION pressed to disable Basic, i get this (see pic)

post-66363-0-49525900-1548584531_thumb.jpg

Link to comment
Share on other sites

First thing I'd do is boot with the drive off and hold OPTION to go to the self test and check that the ram is ok...

 

Is Altirra using a real XL firmware or its internal one, technically for stuff like dos it should not matter but its one thing to check, if its booting Altirra with a real machine firmware and its fine it does sound like its a machine issue, someone more techy on the 600XL with ram modules may know of any oddities it may have?

 

EDIT: Not working on Altirra in XL mode here, it does what you see in the screen just booting the ATR up, I'm pretty sure this is for an older OS like a or b and that would make sense to me with the file names on the disk in 400/800 mode where it works, the files are asmcara.com and asmcarb.com which might suggest one for a OS and one for B OS but they both seemed to work on B any way...

Edited by Mclaneinc
Link to comment
Share on other sites

Reading the wiki page i would think it is ed/asm rev A and rev B?

 

Yup....Sadly as found the image was using a very unfriendly OSA / OSB version, that's what confused me when you said it worked on Altirra in XL mode because it didn't here...

 

Oh well, its all sorted thanks to the good people in here..

 

Have fun

 

Paul..

Link to comment
Share on other sites

How do you fix a real cart that has this problem? Jowi said he was going to use the real cart version on the XL.

 

Interesting conversation and question. I have a real ASEM/ED cart and it works fine with my XL machines and my 1088XEL with an XL or XE OS. Heck, it even runs fine from one of the "BASIC" slots in an Ultimate 1MB.

 

Maybe because it's a cart to begin with (e.g., not sitting in RAM like the disk versions but rather in the usual left cart-mapped 8K address block), it works properly?

Link to comment
Share on other sites

Oh, the wheel of reincarnation again....

 

 

Reading the wiki page i would think it is ed/asm rev A and rev B?

You already asked before, and I replied with a fixed version: http://atariage.com/forums/topic/284609-ed-assem-on-disk/?p=4150015

 

 

 

You're welcome.

 

Bad thing about these Cartridge-images that run in RAM, that you can NOT press RESET.

This will reboot the system and you loose all your work.

So SAVE your work before doing ASM or testing.

Yes, but I also posted a loader than can produce "reset protected" binaries: http://atariage.com/forums/topic/284609-ed-assem-on-disk/?p=4151033

 

Attached is the last version of my rom loader and an ATR with the "reset protected" Assmebler Editor (rev A and rev B)

asmed.atr

romload.s

Edited by dmsc
  • Like 3
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...