Jump to content

Recommended Posts

As started to play around with Amiga OCS coding with a dev chain consisting of VAsm, notepad++ and Winuae I have to say (and I told everybody at Revisiob party) that the combination of MADS, WUDSN IDE plus Altirra is unbeaten in retro coding scene. Try to code for other machines (except PC) and you realise that the Atari 8bitbscene is far away of the pack since peter dell and Avery and tebe combined strength! Thx

 

"Something"?

post-10165-0-59028000-1428756707_thumb.png

 

This is a screen shot of the failed copy to drive D2: (B:). Both from a partition to drive and PCLINK to drive. Copies from partition to partition do copy okay.

Test 5 works okay.

Edited by rdea6

Drive I: is D9: on my ultimate 1mb setup. Also SORTDIR fails also on the mounted ATR, and also CHTD *.*, and any copy to the emulated drive fails. using SDX447 and the same setup Test 5 doesn't have this problem.. Saving a BASIC or LISTED file to emulated drive fails also..on Test 6..

Drive I: is D9: on my ultimate 1mb setup. Also SORTDIR fails also on the mounted ATR, and also CHTD *.*, and any copy to the emulated drive fails. using SDX447 and the same setup Test 5 doesn't have this problem.. Saving a BASIC or LISTED file to emulated drive fails also..on Test 6..

OK. Reproducible here. File is actually copied, but the emulated floppy makes a lot of burps and spits out error 138 at the end of the copy.

Fixed -- accidentally broke one of the write commands while implementing write-verify timing:

http://www.virtualdub.org/beta/Altirra-2.70-test7.zip

http://www.virtualdub.org/beta/Altirra-2.70-test7-src.zip

 

Took a bit longer than expected because I had to track down an intermittent write command retry issue that turned out to be an old Atari OS bug:

  8297:247:107 | A=A0 X=FE Y=31 (N     ) | EA8F: A0 00             LDY #$00
  8297:247:109 | A=A0 X=FE Y=00 (    Z ) | EA91: 84 31             STY CHKSUM
  8297:247:112 | A=A0 X=FE Y=00 (    Z ) | EA93: 84 3B             STY CHKSNT
  8297:248:  1 | A=A0 X=FE Y=00 (    Z ) | EA95: 84 3A             STY $3A
  8297:248:  4 | A=A0 X=FE Y=00 (    Z ) | EA97: B1 32             LDA (BUFRLO),Y ;$1BFC
  8297:248:  9 | A=0E X=FE Y=00 (      ) | EA99: 8D 0D D2          STA SEROUT
- NMI interrupt (VBI)
..
    8297:249: 79 | A=0E X=FE Y=00 (   I  ) | C02C: D8                CLD
    8297:249: 81 | A=0E X=FE Y=00 (   I  ) | C02D: 6C 16 02          JMP (VIMIRQ)
...
    8297:250:107 | A=FF X=FE Y=00 (N  I  ) | 1A12: A0 00             LDY #$00
    8297:250:109 | A=FF X=FE Y=00 (   IZ ) | 1A14: B1 32             LDA (BUFRLO),Y ;$1BFD
    8297:251:  0 | A=40 X=FE Y=00 (   I  ) | 1A16: 8D 0D D2          STA SEROUT
    8297:251:  4 | A=40 X=FE Y=00 (   I  ) | 1A19: 18                CLC
    8297:251:  6 | A=40 X=FE Y=00 (   I  ) | 1A1A: 65 31             ADC CHKSUM
    8297:251:  9 | A=40 X=FE Y=00 (   I  ) | 1A1C: 69 00             ADC #$00
    8297:251: 11 | A=40 X=FE Y=00 (   I  ) | 1A1E: 85 31             STA CHKSUM
    8297:251: 14 | A=40 X=FE Y=00 (   I  ) | 1A20: 4C 0E 1A          JMP $1A0E
    8297:251: 17 | A=40 X=FE Y=00 (   I  ) | 1A0E: 68                PLA
    8297:251: 21 | A=00 X=FE Y=00 (   IZ ) | 1A0F: A8                TAY
    8297:251: 23 | A=00 X=FE Y=00 (   IZ ) | 1A10: 68                PLA
    8297:251: 28 | A=0E X=FE Y=00 (   I  ) | 1A11: 40                RTI
  8297:251: 36 | A=0E X=FE Y=00 (      ) | EA9C: 85 31             STA CHKSUM
  8297:251: 40 | A=0E X=FE Y=00 (      ) | EA9E: A5 11             LDA BRKKEY
  8297:251: 44 | A=80 X=FE Y=00 (N     ) | EAA0: D0 03             BNE $EAA5
  8297:251: 48 | A=80 X=FE Y=00 (N     ) | EAA5: A5 3A             LDA $3A

  • Like 7

fail

post-4806-0-58090500-1428881314.gif

 

 

Actions like w1k's also affects the community as a whole. I know I'm more apprehensive to ask questions because I don't want to come across negative or disrespectful.

 

Yes. I want it to be understood that whatever my apparent tone is; it is always supposed to be viewed as one of a suggestive nature like when asking for new features or changes. Never a demanding one. So forgive me if I get carried away.

I have a serious problem with this 2.70 release. It takes up too much of my time!! Whatta'ya gonna do about it?

 

Make it worse. :)

 

http://www.virtualdub.org/beta/Altirra-2.70-test8.zip

http://www.virtualdub.org/beta/Altirra-2.70-test8-src.zip

  • Tweaks to ATOS S: driver for better compatibility with the XL/XE OS when drawing lines in GR.0 (which people actually do, and which has really weird behavior).
  • Fix for recent regression in debugger that screwed up symbol lookups in the expression evaluator.
  • Fix for a crash in the cartridge code with the MegaCart 1MB (2) mapper that I found by accident.
  • Fix for not being able to drag and drop from the 7-Zip File Manager, which rejects drag requests that use the move cursor. 7zFM always uses a temp file, though, which is not great -- I may need to detect this and force virtual disk mode in that case.
  • Like 6

Sorry, not interested.

 

No problem.

I have realized, that the "direct" layout in Altirra does exactly want I need :)

However the keyboard layout in Windows has to be set to "US" (before I tested with german layout "DE" and the kay mapping didn't have much sense).

I wondered about "Enable Function Keys". How can I access the keys: "HELP","SELECT","START","OPTION" if this feature is enabled?

Thanks

Edited by TheMontezuma

MANY thanks for this Avery!!! I keep meaning to get back in to A8 and assembler and this might just give me the excuse

 

As yet I have not looked at the v2.7 betas. However I will give this stable release a good going over and report anything I find not working or a bit flaky. One thing I really do want to thank you for specifically is the addition of the "DSDD" preset category in the blank disk creator wizard. That is very nice indeed. I may have more to say about that later along with a feature suggestion.

 

For now I am going to run Altirra through its paces making virtual cartridges with the new Spartados v4.47 and so on.

 

On an interesting note, it could be a random thing; just as I am writing this I have the SDX cartridge-writer working in Altirra to flash an 8mbit maxflash virtual cartridge. I am running without the SIO speed-up patch, so it is reading the disk *.ATR at the speed it would in reality and I have the 'disk sound' option selected for ultimate authenticity! However, the disk sound has suddenly stopped. Yet the beeping and the counters show Altirra is still reading and flashing... Perhaps something to look at or maybe a one off? I will try with the different flashers/disk images and report back.

Edited by morelenmir

I am going to post this separately as it may well be a genuine bug.

 

I have 'R-Time 8' selected in the swish new 'Devices' dialogue interface. However my newly flashed "1M (8mbit) MaxFlash Cartridge (newer - bank 0)" version of "SDX 4.47 reports "R-Time 8 Not Present" on boot-up. This is not a problem only present with v4.47 as the same thing happens with versions 4.46 and 4.45.

 

Another update to this. If I then go on to create a new virtual cartridge of the "Empty SIC! Flash Cartridge" type with "SSF39SF040" selected as the flash chip type and flash it with the appropriate SDX 4.47 flasher; no warning about "R-Time 8" being missing is given.

Edited by morelenmir

Hey FJC! I'm glad to see you are still hanging out here!

 

Yep - I do indeed... I wonder why I never encountered that in the past when I have been playing with SDX? Weird!

 

I am pretty sure that will be problem solved, but I will test it out by writing the SIDE1 firmware from the SDX 4.47 flashers and report back.

Edited by morelenmir

This is my recreation in Blender of what having an R-Time 8 and a MaxFlash cartridge in an Atari would look like:

 

post-16457-0-82822900-1429333123_thumb.png

 

There's only one standard slot in an Atari -- you can't have two left carts in it if neither has a pass-through without a hardware mod involving either a soldering iron or a hammer.

 

 

Are there any special steps required to set up MIO, other than attaching the MIO device, then a hard disk, then setting up the firmware? Select+Reset isn't doing anything.

 

 

Nope, that should do it. One possibility is that the dump you have isn't in the order that Altirra is expecting -- attached is a dump that I use.

 

MIO-V141-27256.ROM

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...