TheMontezuma Posted April 8, 2016 Share Posted April 8, 2016 If you want to use the ATR flashers I already released, just replace the ROM file on the ATR with this one. The same ROM is good for SIDE and SIDE2. How can I manipulate the flasher ATR on a PC? The makeATR tool does not support 720kB ATRs Quote Link to comment Share on other sites More sharing options...
Roydea6 Posted April 8, 2016 Share Posted April 8, 2016 (edited) How can I manipulate the flasher ATR on a PC? The makeATR tool does not support 720kB ATRs If you have a hex editor on the PC. Open the atr and edit the 21 to a 20 and then Makeatr will open the atr... It is not the size that is stopping Makeatr just the File type 21 needs to be 20.. Edited April 8, 2016 by rdea6 1 Quote Link to comment Share on other sites More sharing options...
TheMontezuma Posted April 8, 2016 Share Posted April 8, 2016 (edited) Thanks, it helped. Do you know what does the "File Type" number mean? Edited April 8, 2016 by TheMontezuma Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted April 8, 2016 Author Share Posted April 8, 2016 Incognito works fine for me, Thanks. Note that the fix only affected the stand-alone SIDE cart loader, but it's good to know the Incognito loader is working. Everything's working normally! Good - thanks. I'll upload this version to the website. Thanks, it helped. Do you know what does the "File Type" number mean? It's actually the SpartaDOS file system (SDFS) revision number in the boot sector. SDX versions 4.4 onwards put $21 here, but it appears MakeATR only recognizes revision $20 and under. Altirra's disk explorer is the most convenient way (IMO) of editing these ATRs (indeed, Altirra was used to create them). 1 Quote Link to comment Share on other sites More sharing options...
Roydea6 Posted April 8, 2016 Share Posted April 8, 2016 From the 447 SDX manual: $20 (32) File system revision number of the disk format. SD 1.1 has a $11, SD 2.x, 3.x, SDX 4.1x and 4.2x all have a $20 here, SDX 4.4x has $21 here, indicating SDFS version 2.1. 1 Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted April 8, 2016 Author Share Posted April 8, 2016 OK: SIDE/SIDE2 loader 1.03 is on the website (no change to the U1MB/Incognito loader, which I've left at v.1.02 for now), and I've fixed a few small issues with the user manual. Quote Link to comment Share on other sites More sharing options...
danwinslow Posted April 8, 2016 Share Posted April 8, 2016 Thank you Jon for your generosity to the Atari 8-bit community. It really is wonderful when people such as yourself, that have the knowledge and talent, give freely of their time and effort so that we all can benefit. It's good when people help one another in the ways that they can. I'm sure I don't just speak for myself when I say that the A8 community very much appreciates the ways in which you are able to help. As a side note to this very nice post, I'll observe that Jon does have a donate button on his website..... 2 Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted May 7, 2016 Author Share Posted May 7, 2016 Small uFlash update, fixing a nasty bug in the SDX size change function which sometimes erased the entire flash ROM (!): uflash_v.1.22.zip Also on website. 2 Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted May 9, 2016 Author Share Posted May 9, 2016 Another UFLASH update, this time improving support for PCLINK.SYS in the file selector and allowing default logged devices other than DSK: (supported by the forthcoming SDX 4.48): uflash_v.1.24.zip 5 Quote Link to comment Share on other sites More sharing options...
Marius Posted May 10, 2016 Share Posted May 10, 2016 Sounds like a smooth update to me 1 Quote Link to comment Share on other sites More sharing options...
Roydea6 Posted May 16, 2016 Share Posted May 16, 2016 Another UFLASH update, this time improving support for PCLINK.SYS in the file selector and allowing default logged devices other than DSK: (supported by the forthcoming SDX 4.48): uflash_v.1.24.zip Jon, Has any one else reported problems with the flasher trying to enter another folder from default. TO update a rom slot?? Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted May 16, 2016 Author Share Posted May 16, 2016 Jon, Has any one else reported problems with the flasher trying to enter another folder from default. TO update a rom slot?? No, but it's probably untested with PCL:, so might be a bug. I'll check it out - thanks Roy! Quote Link to comment Share on other sites More sharing options...
Roydea6 Posted May 16, 2016 Share Posted May 16, 2016 By the way It did not happen with the emulator[ALTIRRIA] just real hard ware, and might be my fat fingering .. I CDed into the folder with the correct rom and then called uflash and this worked. Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted May 16, 2016 Author Share Posted May 16, 2016 I changed the file selector to accommodate longer device names so wouldn't be surprised if I broke it. Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted May 16, 2016 Author Share Posted May 16, 2016 By the way It did not happen with the emulator[ALTIRRIA] just real hard ware, and might be my fat fingering .. I CDed into the folder with the correct rom and then called uflash and this worked. Just tested the latest UFLASH with SDX 4.47 on real hardware and I can't duplicate a problem entering a folder on PCL: using the file selector. Can you reproduce? Quote Link to comment Share on other sites More sharing options...
Roydea6 Posted May 16, 2016 Share Posted May 16, 2016 False alarm I tried my second 800xl with U1M and It Flashed ok.. I put the better 800xl back in service and had no problems changing folders from the Flasher Dialogue screen. The better one is better only because of the nice s-video 1 Quote Link to comment Share on other sites More sharing options...
+mytek Posted May 16, 2016 Share Posted May 16, 2016 OK I got a problem with updating to the new bios. So here's the scenario... I have a U-1Meg with the much older bios in it (I think it is pre any of FJC's versions, probably Candle's). Anyway I downloaded the latest zipped Alt-bios file from FJC's site, unzipped it, moved the ROM and UFLASH files into a SpartaDos formatted ATR, and then booted up the computer with SIO2PC-USB pointing to that ATR. SDX loads up from the U-1Meg, and I can directory that ATR, so far so good. Next I reboot the computer with HELP held down, entering the U-1Meg config menu, proceed to select 1088k RAMBO for memory, SDX enabled, and all other hardware disabled. I save it ('S' key), and quit ('Q' key) which reloads SDX. Now I load UFLASH.XEX... I get the following message: Cannot identify hardware. Select manually? OK or CANCEL I hit Return for OK and this brings up a Select Device sub menu, with Ultimate 1MB at the top of the list. I leave that highlighted, and use the TAB key to put me at OK, and then I hit the Return key which simply brings up the same "Cannot identify hardware" I saw before. I try it all again, but keep coming back to the same message (going around in circles). So I TAB'ed to CANCEL and hit Return which bails me out of the message window and a list scrolls into place with a 'No Device' header, although it appears to be listing everything that is in my U-1Meg. So I'm kind of stuck. Would love to proceed with the re-flash, but can't. Anyone have a clue as to what I am doing wrong? - Michael Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted May 16, 2016 Author Share Posted May 16, 2016 Any others carts/ROMs present? I assume you're using the version of UFLASH included in the BIOS archive. The BIOS on your board may be so old that the flasher can't pick up any signature info at all, and it may no longer handle this scenario so well. It's becoming a pain managing both generations of firmware... Don't suppose you can post a dump of the whole ROM? Might be useful to see what's happening. 1 Quote Link to comment Share on other sites More sharing options...
+mytek Posted May 16, 2016 Share Posted May 16, 2016 (edited) Hi Jon , I got this particular U-1Meg from a friend. He did configure it with various ROMs. So here's the list I'm seeing... XL/XE OS1: Warp OS XL/XE OS2: Multiplexer XL/XE OS3: Q-Meg OS XL/XE OS4: Stock OS BASIC SLOT1: BASIC BASIC SLOT2: Assembler BASIC SLOT3: Defender BASIC SLOT4: CAR3 XEGS SLOT1: Missle Command XEGS SLOT2: River Raid XEGS SLOT3: Defender XEGS SLOT4: CAR 3 How would I go about doing a dump of the ROM as you requested? BTW, this board is installed on an XEGS. - Michael EDIT: yes I'm using the UFLASH from within the zipped archive I just got off of your site today. Edited May 16, 2016 by mytekcontrols Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted May 16, 2016 Author Share Posted May 16, 2016 You could try highlighting the chip name right at the top of the list and choosing dump slot from the menu (or pressing D). That ought to let you write the whole 512KB to a file. Quote Link to comment Share on other sites More sharing options...
+mytek Posted May 16, 2016 Share Posted May 16, 2016 (edited) You could try highlighting the chip name right at the top of the list and choosing dump slot from the menu (or pressing D). That ought to let you write the whole 512KB to a file. Here you go: MY.ROM - Michael EDIT: Pretty friggin slick BTW Edited May 16, 2016 by mytekcontrols 1 Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted May 17, 2016 Author Share Posted May 17, 2016 I can see what's happening here. Previously, when manually selecting the device the program just went along with your choice, but now that there are two different revisions of the firmware, it still probes for signature information even following a manual override. Very old firmware with no signature information of any kind fails all the tests. I'll have to code around this... should get a fix sorted tomorrow. 2 Quote Link to comment Share on other sites More sharing options...
Roydea6 Posted May 17, 2016 Share Posted May 17, 2016 (edited) Here you go: MY.ROM - Michael EDIT: Pretty friggin slick BTW I stuck the rom into Altirria and did the bios, loader, PBI, and Myversion of the latest SDX447.rom MY.ROM I left all the other config. stuff for you to play with.. Good Luck PS I would get rid of all the OS roms except the Stock OS. The others are not PBI compliant. And you have my version of Atari Basic. The reason I say this is that The rom is going into an XEGS. Find and use Hias Hi Speed rom. as one of your OS slots. Edited May 17, 2016 by rdea6 4 Quote Link to comment Share on other sites More sharing options...
+mytek Posted May 17, 2016 Share Posted May 17, 2016 (edited) I can see what's happening here. Previously, when manually selecting the device the program just went along with your choice, but now that there are two different revisions of the firmware, it still probes for signature information even following a manual override. Very old firmware with no signature information of any kind fails all the tests. I'll have to code around this... should get a fix sorted tomorrow. Sounds good. So with that in mind, should I use rdea's ROM? And if so, will that fix things? Note: I have the prompt up that says "Completely rewrite flash ROM? Slot descriptions will be lost. OK CANCEL". So keep in mind that this is my first time using UFLASH (should I take the red pill or the blue pill ). I stuck the rom into Altirria and did the bios, loader, PBI, and Myversion of the latest SDX447.rom MY.ROM I left all the other config. stuff for you to play with.. Good Luck PS I would get rid of all the OS roms except the Stock OS. The others are not PBI compliant. And you have my version of Atari Basic. The reason I say this is that The rom is going into an XEGS. Find and use Hias Hi Speed rom. as one of your OS slots. Thank you for doing that . - Michael Edited May 17, 2016 by mytekcontrols Quote Link to comment Share on other sites More sharing options...
oracle_jedi Posted May 17, 2016 Share Posted May 17, 2016 (edited) I used this latest updater and the 2016/04 Incognito Firmware Package from http://atari8.co.uk/firmware/incognito to update my Incognito on an NTSC 800. The XL self-test no longer executes the sound test correctly. Is that expected behaviour or did I miss a step? This is my first time trying to flash the Incognito using the uflash tool. Edited May 17, 2016 by oracle_jedi Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
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.