flashjazzcat Posted January 10, 2014 Author Share Posted January 10, 2014 Might have something to test by Sunday: Editing the descriptions will incur a re-flash of the relevant ROM sector; i.e. the existing data will be cached and re-flashed to the chip. When a new BIOS ROM is loaded, the existing descriptions will therefore persist (they'll be merged into the new ROM data). This is all Ultimate 1MB so far: Incognito will be handled once Ultimate is working correctly. 2 Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted January 19, 2014 Author Share Posted January 19, 2014 Latest FDISK build: fdisk42.zip 2 Quote Link to comment Share on other sites More sharing options...
atari8warez Posted January 20, 2014 Share Posted January 20, 2014 (edited) Jon, yesterday I've tried fdisk v4.2 with my IDE+2, now even though I have valid partitions in my CF card (a FAT16 and a APT partition with drive numbers D8: and D3: respectively) when I boot I am getting device timeout errors (138) on my IDE+2 drives. When I restart FDISK and take a look at my partitions I can't see anything obviously wrong but yet no matter how many times I repeat the partioning I end up with the same result. I am not sure if this has anything to do with FDISK but I even flushed the BIOS thinking it may be a hardware related problem, still the same result. Now let me tell you what exactly happened. Yesterday the device was working fine on my 800XL with U1MB and IDE+2 (both on the same machine at the same time), what I noticed though if both upgrades had high-speed turned ON, my computer was locking up whenever I tried to access SIO drives (PBI drives were OK). So I turned ultraspeed OFF in IDE+2 setup screen and SIO drives started to work, then I wanted to try your new release of FISK v4.2 (at that point my CF card was portioned with FDISK4 Beta 9). The problems started after I ran new FDISK, honestly I don't remember if I initialized the CF card the first time I used the new FDISK or simply updated existing partition tables, however after I've seen that I am getting error 138 the card has been reinitialized several times with new partition tables on it but error 138 did not go away no matter what I did. I also tried to move IDE+2 to my 130XE with a built-in SIO2PC but no other upgrades on it, same results there too (error 138). I examined the partitions on the CF card with my Windows laptop and they are there and the FAT16 is accessible by Windows. Here's a video and a snapshot of my IDE+2 settings, i hope they may help. Edited January 20, 2014 by atari8warez Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted January 20, 2014 Author Share Posted January 20, 2014 You need an IDE Plus 2.0 BIOS update from Konrad. PM him and I'm sure he'll oblige. The latest FDISK sets a flag in the APT header which is incompatible with the current IDE Plus 2.0 BIOS. The flag is discussed at length earlier in this thread, and I warned IDE Plus users that they need to DISABLE the Global MetaData Flag in APT->Properties until the updated BIOS is released. So: either turn off the global metadata flag for the moment, or ask KMK if he'll send you an intermediate BIOS update. Quote Link to comment Share on other sites More sharing options...
atari8warez Posted January 20, 2014 Share Posted January 20, 2014 You need an IDE Plus 2.0 BIOS update from Konrad. PM him and I'm sure he'll oblige. The latest FDISK sets a flag in the APT header which is incompatible with the current IDE Plus 2.0 BIOS. The flag is discussed at length earlier in this thread, and I warned IDE Plus users that they need to DISABLE the Global MetaData Flag in APT->Properties until the updated BIOS is released. So: either turn off the global metadata flag for the moment, or ask KMK if he'll send you an intermediate BIOS update. Ooops! must have missed that bit of information, thanks a lot, I will turn the metadata flag off and try it again. Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted January 20, 2014 Author Share Posted January 20, 2014 BTW: forget about HDDINFO. It's deprecated, buggy and will be replaced. Quote Link to comment Share on other sites More sharing options...
atari8warez Posted January 20, 2014 Share Posted January 20, 2014 So: either turn off the global metadata flag for the moment, or ask KMK if he'll send you an intermediate BIOS update. Ok, I've done the partitioning all over again and now APT partition is OK and I can access D3:, however the FAT16 partition (with drive-id D8:) is still giving me error 138, do I also need a new version of FATFS.SYS? Quote Link to comment Share on other sites More sharing options...
atari8warez Posted January 20, 2014 Share Posted January 20, 2014 (edited) BTW: forget about HDDINFO. It's deprecated, buggy and will be replaced. How about PARTINFO.COM?, it does not display anything, just makes a disk polling noise. Edited January 20, 2014 by atari8warez Quote Link to comment Share on other sites More sharing options...
Roydea6 Posted January 20, 2014 Share Posted January 20, 2014 hi Are the DLL files still needed in the path like the previous Fdisk. Quote Link to comment Share on other sites More sharing options...
drac030 Posted January 20, 2014 Share Posted January 20, 2014 Ok, sorry for the delay. I may as well release what I have now, as it seems that the updated APT support is both working (I heard no complaints on it from the testers), and that it is really necessary, as the 1.2 became outdated. So, IDE+ BIOS v.1.3 below. It is an ARC file renamed ZIP, as usual. NEWS.TXT contains a list of changes. As usual, not everything was done what was requested - apologies! - but time urges. I hope that the remaining fixes will come into a next version. bios1801.zip 4 Quote Link to comment Share on other sites More sharing options...
atari8warez Posted January 20, 2014 Share Posted January 20, 2014 Ok, sorry for the delay. I may as well release what I have now, as it seems that the updated APT support is both working (I heard no complaints on it from the testers), and that it is really necessary, as the 1.2 became outdated. So, IDE+ BIOS v.1.3 below. It is an ARC file renamed ZIP, as usual. NEWS.TXT contains a list of changes. As usual, not everything was done what was requested - apologies! - but time urges. I hope that the remaining fixes will come into a next version. Conrad, I am getting archive damaged or corrupt error. Tried downloading a few times Quote Link to comment Share on other sites More sharing options...
drac030 Posted January 20, 2014 Share Posted January 20, 2014 It is not a ZIP file, it is an ARC file. I only named it so, because the forum does not allow me to attach *.ARC. Quote Link to comment Share on other sites More sharing options...
atari8warez Posted January 20, 2014 Share Posted January 20, 2014 (edited) It is not a ZIP file, it is an ARC file. I only named it so, because the forum does not allow me to attach *.ARC. Ok, I'll try my IZArc then Edited January 20, 2014 by atari8warez Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted January 20, 2014 Author Share Posted January 20, 2014 hi Are the DLL files still needed in the path like the previous Fdisk. Nope. Throw the DLLs away. I have a version of FDISK 4 which fits on CAR as well. Will release soon. 1 Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted January 20, 2014 Author Share Posted January 20, 2014 (edited) How about PARTINFO.COM?, it does not display anything, just makes a disk polling noise. Likewise: bin it and use Konrad's DISKINFO.COM. BTW: it should be implied that all the latest tools from this side of things will soon find their way into a cohesive package hosted on my website. Naturally it's taken a long time to reach this stage, but hopefully people are appreciative of the rather huge amount of R&D which has gone on during the last couple of years. Edited January 20, 2014 by flashjazzcat 1 Quote Link to comment Share on other sites More sharing options...
Roydea6 Posted January 20, 2014 Share Posted January 20, 2014 Ok, I'll try my IZArc then IZarc is a great tool for the windows computer, but why not use ASPEQT folder mount and copy the Bios.arc file straight into the IDE20 Partition and use SpartaDos ARC E BIOS.arc to extract .. 1 Quote Link to comment Share on other sites More sharing options...
Kyle22 Posted January 20, 2014 Share Posted January 20, 2014 It is not a ZIP file, it is an ARC file. I only named it so, because the forum does not allow me to attach *.ARC. *.ARC works now (Thanks Al). 2 Quote Link to comment Share on other sites More sharing options...
+Stephen Posted January 20, 2014 Share Posted January 20, 2014 Likewise: bin it and use Konrad's DISKINFO.COM. BTW: it should be implied that all the latest tools from this side of things will soon find their way into a cohesive package hosted on my website. Naturally it's taken a long time to reach this stage, but hopefully people are appreciative of the rather huge amount of R&D which has gone on during the last couple of years. Last couple of years - wow, time does fly. The past few years have been the most active Atari times I have experienced since the early 80s - it's been great fun. 1 Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted January 21, 2014 Author Share Posted January 21, 2014 Last couple of years - wow, time does fly. The past few years have been the most active Atari times I have experienced since the early 80s - it's been great fun. Yeah, it might be more actually: I think I wrote the first version of FDISK for the SDX MyIDE driver in September 2010. Anyway, last November it was five years since my return to this hobby, and these have been among the busiest, most creative, and most fun five years of my life. 1 Quote Link to comment Share on other sites More sharing options...
drac030 Posted January 22, 2014 Share Posted January 22, 2014 *.ARC works now (Thanks Al). I somehow overlooked this post. But the news is very cool, thanks! Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted January 24, 2014 Author Share Posted January 24, 2014 (edited) Another pretty rough test version, this time of the heavily revised MATR: matr.xex Since this basically duplicates the ATR mounting functionality of the XEX loader (without the ability to load XEX files), I've added some experimental support for dynamic APT partition mounting via the same UI. Once you've chosen the device, next select the desired partition type (FAT or APT), and depending on the selection you'll either get a list of disk images in the FAT or a list of named (and only the named) APT partitions on the disk. You can assign and remove drive numbers at will, boot ATRs, or simply drop back to DOS and work with the ATRs or partitions. Note that several things don't work (APT partition properties and Unmount all drives to name but two), but it shouldn't take long to get the application into an acceptable state. The functionality it provides will probably become slightly deprecated once we get SDX access to FAT32 partitions (since we already have access to FAT16 partitions, I provided a simple demo tool which mounts ATRs with Ultimate/Incognito direct from the command line here), but for now it may prove useful to some. Apologies for the mandatory device selection dialogue at the start: it's unlikely that more than one ATR-capable device would be connected at any one time, and I'll eventually skip the manual device selection if only a single APT device is detected. It proved useful during development, however. Edited January 24, 2014 by flashjazzcat Quote Link to comment Share on other sites More sharing options...
w1k Posted January 24, 2014 Share Posted January 24, 2014 first time i run matr without X, then i choose FAT32, i go to the directory.. then i swich to APT and no directories.. then i exit and C: not exist.. hmm Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted January 24, 2014 Author Share Posted January 24, 2014 Do your APT partitions have names? If not, they won't show up in the APT list (I mentioned this in the posting above). Losing C: is odd... clearly it was unmounted somehow. Try with named partitions and see if they show up, like this: Any issues with the FAT directory and ATRs? Quote Link to comment Share on other sites More sharing options...
Roydea6 Posted January 24, 2014 Share Posted January 24, 2014 Nothing but GOOD reports for the matr.xex so far, I have only done the Fat32. Next after dinner I will check the APT.. 1 Quote Link to comment Share on other sites More sharing options...
Roydea6 Posted January 25, 2014 Share Posted January 25, 2014 Now I need a (for instance) why would I ever need to Mount and already mounted partition from the APT portion of my CF card. Example please! 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.