Jump to content
phaeron

Altirra 2.70 released

Recommended Posts

Is it possible to use the mouse as input for PADDLE(0) and PADDLE(1)? I can only seem to get PADDLE(0) response:

 

10 ? PADDLE(0),PADDLE(1)

20 GOTO 10

 

Only the first column of numbers changes.

 

Yes, but you need to customize the input maps. You want a second input map, or another controller within the same input map, that has Paddle B with the paddle knob mapped to one of the vertical mouse inputs. The exact input depends on what kind of mapping you want. Both absolute (screen position -> paddle value) and relative (movement -> paddle rotation) are possible.

  • Like 1

Share this post


Link to post
Share on other sites

 

  • PCLink fixes. Renaming should now return the correct status code and directories should be readable as byte streams instead of just FFIRST/FNEXT.

 

It is much better now, thank you. But, eventhough the documentation suggests to pass a file mask to the OPEN call, the contents of the data stream should not be filtered. In other words, the mask passed to the OPEN call should be ignored, and the data stream should provide all the contents of the directory file.

Share this post


Link to post
Share on other sites

I'm using the switchable XEGS cart version of Turbo Basic found here (at the bottom of the page).

However these step work OK in Altirra Basic so I unsure as to what the issue maybe.

System / Devices menu and "Host Device ( H: )" dialog

 

1) If "Also install as D:" is checked and the system is booted then D: isn't mapped. Turbo Basic "DIR" command returns Err. 160

 

2) Bring up the dialog and uncheck "Also install as D:". Turbo Basic "DIR" command returns Err. 130

 

3) Bring up the dialog and check "Also install as D:" again. Turbo Basic "DIR" command now correctly displays the directory listing.

 

Another clue:

 

a) If launching a MyDos disk menu but then detaching D1: a 163 error is given when trying to read the directory.

 

b) Uncheck "Also install as D:" / OK / Check / OK then permits the directory to be read again.

 

c) If you re-attach the MyDos disk, the H: drive content is still listed rather than that of the inserted drive.

 

Thanks,

Mark

Edited by Wrathchild

Share this post


Link to post
Share on other sites

 

Yes, but you need to customize the input maps. You want a second input map, or another controller within the same input map, that has Paddle B with the paddle knob mapped to one of the vertical mouse inputs. The exact input depends on what kind of mapping you want. Both absolute (screen position -> paddle value) and relative (movement -> paddle rotation) are possible.

Go it! Thanks.

Share this post


Link to post
Share on other sites

Oops. Had to rewrite the way FNEXT works to fix it, but try now:

 

Yes, it seems to work now as expected, thank you.

 

Some other thing: the debugger does not seem to react properly on breakpoints-on-access set for the addresses past the first 64k. Example:

 

ba w $02c000

g

 

From SDX prompt: POKE $02C000,$FF - no reaction.

 

Same problem with ba r $02c000, later PEEK $02C000 - no reaction.

 

Also the memory windows (Debug->Window->Memory) do not seem to allow peeking into the addresses higher than $FFFF.

 

All in the 65C816 mode, 4 MB extra RAM enabled.

Share this post


Link to post
Share on other sites

I'm using the switchable XEGS cart version of Turbo Basic found here (at the bottom of the page).

However these step work OK in Altirra Basic so I unsure as to what the issue maybe.

System / Devices menu and "Host Device ( H: )" dialog

 

1) If "Also install as D:" is checked and the system is booted then D: isn't mapped. Turbo Basic "DIR" command returns Err. 160

 

This cartridge installs its own DOS D: handler, which conflicts with the emulator's. You can't use both at the same time.

 

Some games, like "GETAWAY" in full screen mode: If I move to the left or right, the graphics are not nice (sync?).

 

Uh, "not nice"? I need a better description than that. Not seeing a problem here.

 

 

Some other thing: the debugger does not seem to react properly on breakpoints-on-access set for the addresses past the first 64k. Example:

 

Yes, apologies, some parts of the emulator are still not '816 aware and the breakpoint system is one of them. I've been fixing that slowly.

  • Like 2

Share this post


Link to post
Share on other sites

Phaeron, there are some atr's posted in the Jumpman hacking thread located here http://atariage.com/forums/topic/252267-jumpman-hacking/?do=findComment&comment=3504131

 

They use a K loader and don't load on Altirra but do work on Atariwin 800 Plus, I've tried as much as I can to make them work.

 

Am I correct in thinking these images would not work on a real machine? (my hardware isn't hooked up at the mo)

Share this post


Link to post
Share on other sites

Some games, like "GETAWAY" in full screen mode: If I move to the left or right, the graphics are not nice (sync?).

 

 

Just tried your atr and I'm not seeing what you mean?

 

You said sync so I'm presuming there's tearing, I'd suggest under View that you turn on Vsync but the chances are its an issue your end, even with Vsync its smooth as silk here..

Share this post


Link to post
Share on other sites

Very small gripe/maybe bug. I am using the newest Altirra release, the PCL: emulator, SDX and its PCLink driver.

 

Under BASIC I issue this command after typing in a programme:

SAVE "DPCL:FILENAME.BAS"

In return I get a high-pitched and extremely annoying whistle during the writing process. I next enter:

LIST "DPCL:FILENAME.LST"

Interestingly, this time I get no whistle at all. I have not experimented with PCLink before so do not know if this is normal. However it is quite painful!!!

Share this post


Link to post
Share on other sites

Phaeron, there are some atr's posted in the Jumpman hacking thread located here http://atariage.com/forums/topic/252267-jumpman-hacking/?do=findComment&comment=3504131

 

They use a K loader and don't load on Altirra but do work on Atariwin 800 Plus, I've tried as much as I can to make them work.

 

Am I correct in thinking these images would not work on a real machine? (my hardware isn't hooked up at the mo)

I was able to boot the "less mysterious.atr" ATR in that post by adding exactly 99 bytes of zero to the end of it. Any less and it crashes.

 

It's failing on a SIOV call with error 139 ($8B) Device NAK with the short ATR:

 

31) T=07673| 65,108 A=31 X=FE Y=80 S=F9 P=30 ( ) 0808: A9 01 LDA #$01
30) T=07673| 65,110 A=01 X=FE Y=80 S=F9 P=30 ( ) 080A: 8D 01 03 STA DUNIT [$0301]
29) T=07673| 66, 0 A=01 X=FE Y=80 S=F9 P=30 ( ) 080D: A9 52 LDA #$52
28) T=07673| 66, 2 A=52 X=FE Y=80 S=F9 P=30 ( ) 080F: 8D 02 03 STA DCOMND [$0302]
27) T=07673| 66, 6 A=52 X=FE Y=80 S=F9 P=30 ( ) 0812: A9 40 LDA #$40
26) T=07673| 66, 8 A=40 X=FE Y=80 S=F9 P=30 ( ) 0814: 8D 03 03 STA DSTATS [$0303]
25) T=07673| 66, 12 A=40 X=FE Y=80 S=F9 P=30 ( ) 0817: A9 80 LDA #$80
24) T=07673| 66, 14 A=80 X=FE Y=80 S=F9 P=B0 (N ) 0819: 8D 04 03 STA DBUFLO [$0304]
23) T=07673| 66, 18 A=80 X=FE Y=80 S=F9 P=B0 (N ) 081C: A9 08 LDA #$08
22) T=07673| 66, 20 A=08 X=FE Y=80 S=F9 P=30 ( ) 081E: 8D 05 03 STA DBUFHI [$0305]
21) T=07673| 66, 32 A=08 X=FE Y=80 S=F9 P=30 ( ) 0821: A9 1F LDA #$1F
20) T=07673| 66, 40 A=1F X=FE Y=80 S=F9 P=30 ( ) 0823: 8D 06 03 STA DTIMLO [$0306]
19) T=07673| 66, 56 A=1F X=FE Y=80 S=F9 P=30 ( ) 0826: A9 80 LDA #$80
18) T=07673| 66, 62 A=80 X=FE Y=80 S=F9 P=B0 (N ) 0828: 8D 08 03 STA DBYTLO [$0308]
17) T=07673| 66, 70 A=80 X=FE Y=80 S=F9 P=B0 (N ) 082B: A9 00 LDA #$00
16) T=07673| 66, 74 A=00 X=FE Y=80 S=F9 P=32 ( Z ) 082D: 8D 09 03 STA DBYTHI [$0309]
15) T=07673| 66, 82 A=00 X=FE Y=80 S=F9 P=32 ( Z ) 0830: AD 77 08 LDA $0877 [$0877] = $BA
14) T=07673| 66, 90 A=BA X=FE Y=80 S=F9 P=B0 (N ) 0833: 8D 0A 03 STA DAUX1 [$030A]
13) T=07673| 66, 98 A=BA X=FE Y=80 S=F9 P=B0 (N ) 0836: AD 78 08 LDA $0878 [$0878] = $00
12) T=07673| 66,103 A=00 X=FE Y=80 S=F9 P=32 ( Z ) 0839: 8D 0B 03 STA DAUX2 [$030B]
11) T=07673| 66,107 A=00 X=FE Y=80 S=F9 P=32 ( Z ) 083C: 20 59 E4 JSR SIOV [$E459] = $4C
10) T=07673| 66,113 A=00 X=FE Y=8B S=F7 P=B1 (N C) E459: -- High level emulation --
9) T=07673| 67, 5 A=00 X=FE Y=8B S=F9 P=B1 (N C) 083F: AD 03 03 LDA DSTATS [$0303] = $8B
 T=07673| 67, 9 A=8B X=FE Y=8B S=F9 P=B1 (N C) 0842: C9 02 CMP #$02
7) T=07673| 67, 11 A=8B X=FE Y=8B S=F9 P=B1 (N C) 0844: B0 22 BCS $0868
6) T=07673| 67, 14 A=8B X=FE Y=8B S=F9 P=B1 (N C) 0868: A0 01 L0868 LDY #$01
5) T=07673| 67, 16 A=8B X=FE Y=01 S=F9 P=31 ( C) 086A: 8C 76 08 STY $0876 [$0876]
4) T=07673| 67, 20 A=8B X=FE Y=01 S=F9 P=31 ( C) 086D: 38 SEC
3) T=07673| 67, 24 A=8B X=FE Y=01 S=F9 P=31 ( C) 086E: 60 RTS
2) T=07673| 67, 48 A=8B X=FE Y=01 S=FB P=31 ( C) 073F: B0 CC BCS $070D
1) T=07673| 67, 60 A=8B X=FE Y=01 S=FB P=31 ( C) 070D: A9 46 L070D LDA #$46
0) T=07673| 67, 64 A=46 X=FE Y=01 S=FB P=31 ( C) 070F: 8D C6 02 STA COLOR2 [$02C6]

Share this post


Link to post
Share on other sites

The last sector is short 100 bytes, so I'm surprised 99 bytes worked, but you're right, the last sector needs to be padded out.

Share this post


Link to post
Share on other sites

hello

 

is there a tutorial for newbies to use Altirra ?

i never got an atari 800 so i don't know how to use it.

 

my keyboard doesn't respond. oO

 

16050607075816744214205152.jpg

Edited by greatxerox

Share this post


Link to post
Share on other sites

Not sure what the cause is, but in Altirra, cold power-on goes to Self Test with this Ultimate 1MB BIOS with basically everything turned off (including SDX) and the BASIC slot set to Atari BASIC (with stock XL/XE OS):

 

Ultimate1MBNew.rom

 

On real hardware using the same config, the machine powers on direct to BASIC as hoped. Something to do with the default state of PORTB? Unsure.

Share this post


Link to post
Share on other sites

Some games, like "GETAWAY" in full screen mode: If I move to the left or right, the graphics are not nice (sync?).

 

 

 

A friend has another PC with Windows XP. when the cars moves, the buildings (and other objects) look like this:

 

geta2.png

 

I don't know if this always happens.

 

With Win 7 (my Pc), works well.

Share this post


Link to post
Share on other sites

Yes there is. This forum and the "How To Use" section in the help file should be able to answer all your questions.

Share this post


Link to post
Share on other sites

Not sure what the cause is, but in Altirra, cold power-on goes to Self Test with this Ultimate 1MB BIOS with basically everything turned off (including SDX) and the BASIC slot set to Atari BASIC (with stock XL/XE OS):

 

attachicon.gifUltimate1MBNew.rom

 

On real hardware using the same config, the machine powers on direct to BASIC as hoped. Something to do with the default state of PORTB? Unsure.

D'Oh... ignore that. I had BASIC disabled in Firmware options. :)

Share this post


Link to post
Share on other sites

Very small gripe/maybe bug. I am using the newest Altirra release, the PCL: emulator, SDX and its PCLink driver.

 

Under BASIC I issue this command after typing in a programme:

SAVE "DPCL:FILENAME.BAS"

In return I get a high-pitched and extremely annoying whistle during the writing process. I next enter:

LIST "DPCL:FILENAME.LST"

Interestingly, this time I get no whistle at all. I have not experimented with PCLink before so do not know if this is normal. However it is quite painful!!!

 

PCLink is a serial I/O bus device and therefore the usual SIO tones apply. The read tone is ~960Hz at standard speed, while the write tone is inaudible. PCLink is also capable of much longer transfers than a disk drive, which is why it's a single continuous tone.

 

There are two ways around this problem. The first is to use /S when loading PCLINK.SYS, which will cause the PCLink driver to use regular SIO routines in a way that the emulator can accelerate. The downside to this is that there have been issues in the past with data corruption when the driver attempts to transfer in the banking window in this mode. The other way is to enable SIO burst transfers for the "Other" category, which will allow the PCLink driver to transfer as fast as possible and push the tone up out of the audible range.

 

The last sector is short 100 bytes, so I'm surprised 99 bytes worked, but you're right, the last sector needs to be padded out.

 

Ugh. Well, I suppose I can just pad out the disk image on load.

 

 

A friend has another PC with Windows XP. when the cars moves, the buildings (and other objects) look like this:

 

geta2.png

 

I don't know if this always happens.

 

With Win 7 (my Pc), works well.

 

'This'? Are you referring to the one pixel shift near the top? Please be specific when referring to issues.

 

Vertical sync (VSYNC) is required to avoid tearing. In Windows XP, this is only reliable in full screen mode and with a 3D capable video card. Altirra does not support true full screen mode with DirectDraw and so you will get tearing without a 3D accelerator.

Share this post


Link to post
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...