+CharlieChaplin Posted February 25, 2019 Share Posted February 25, 2019 (edited) I'll give up what I can find on the XF551 hacks. The XF359693 seems to have all the fixes. The others, who knows? Bob XF551ROM.zip Hmmm, is one of these files the patched XF ROM for 3,5" / 720k drives, as mentioned in this posting: https://groups.google.com/forum/#!topic/comp.sys.atari.8bit/3pf7Z-aNjj0 (or as I call it, XF720k.ROM with latest patch by Bob Woolley). A small info-text what was changed in each XF ROM (and if it's for 360k or 720k) would be very nice... Edited February 25, 2019 by CharlieChaplin 1 Quote Link to comment Share on other sites More sharing options...
+bob1200xl Posted February 25, 2019 Share Posted February 25, 2019 There is that little DOC I've been looking for! That should be the XF350603 file, yes. If you compare the stock ROM with the altered locations, it should be one of those files. Bob 2 Quote Link to comment Share on other sites More sharing options...
_The Doctor__ Posted February 26, 2019 Share Posted February 26, 2019 there was also a patch for sparta dos that I shared on AA that allowed booting a stock xf551 rom without power cycling or pressing reset. It allowed booting the DD disks without incident first time every time. The XF was purposely was stubborn about density change to allow copy protected software for the 810/1050 to run on it at that time. If those fixes still allow for that then I might upgrade to them, if not then I'll leave it stock and use properly patched DOS that understands the XF and switches it just fine anyway... Quote Link to comment Share on other sites More sharing options...
1050 Posted February 26, 2019 Share Posted February 26, 2019 Thanks Bob, it's quite the bundle you dropped on us too. First, XF350603 file is actually four repeats of itself as if it were meant for a 27128 eprom. At any rate that's what I had to prove first and then I had to append 4K of zeros to the end of that quarter to make a file that would compare well to the stock 38B97AE3 rom and then compare those. Only I made a mistake and used the 360K file I posted above in #26, but it still works to show something I was not expecting: Comparing files XF360.BIN and bobs1.bin 0000006E: 04 00 0000006F: FA BB 000000FA: BB FF 000000FB: 07 FF 000000FC: EB FF 000000FD: FC FF 000000FE: 04 FF 000000FF: 73 FF 00000250: 44 00 00000251: EE 00 000002A4: 44 00 000002A5: EC 00 000002EC: 44 FF 000002ED: A7 FF 000002EE: 44 FF 000002EF: 53 FF these below are accounted for as 3.5 values and are last best version values by Bob Woolley 0000053D: 00 03 Lee has never seen the different bytes above however - the missing PAL rom? 0000057B: 18 1B 0000061D: F6 F4 00000621: F6 F4 00000680: 28 50 0000080F: 30 60 00000811: FD FA 000009D1: 08 0B 00000B15: 18 1B 00000D0D: A2 A0 To help me keep this all straight, I long ago pasted the last best version values into the Len Spencer dialog text and it looks like this. ------------------------------------ There is a little bug in the code that allows the drive to start writing the track before it has reached operating speed. To remedy that, change $528 from $90 to $00, $C1D from $88 to $80, * skip $E25 from $88 to $80. * skip [i have heard reports that this may be unnecessary, so you may or may not want to make the aforementined changes. I have had the problem, so better safe than sorry. - L.S.] The 720K drive has 80 tracks per side which requires you to change $680 from $28 to $50, $80F from $30 to $60, $811 from $FD to $FA. A 3.5 inch drive uses a 3ms seek time -- change $53D from $00 to $03, $57B from $18 to $13, *1b $9D1 from $08 to $03, *0b $B15 from $18 to $13. *1b Finally, the 3.5s use write pre-compensation -- change $61D from $F6 to $F4, $621 from $F6 to $F4 $D0D from $A2 to $A0. ------------------------ Bob's latest values are denoted by the * asterisk. So a little more digging around in your files and I find XF551ROM.DAT: Comparing files 38B97AE3.bin and XF551ROM.DAT <<<<<<<CRC-32 D438B4D9 0000006E: 04 00 0000006F: FA BB 000000FA: BB FF 000000FB: 07 FF 000000FC: EB FF 000000FD: FC FF 000000FE: 04 FF 000000FF: 73 FF 00000250: 44 00 00000251: EE 00 000002A4: 44 00 000002A5: EC 00 000002EC: 44 FF 000002ED: A7 FF 000002EE: 44 FF 000002EF: 53 FF I highly suspect this is the PAL rom, I really do. So to that end I have made a XF-720kw.bin file ready for use with the CRC-32 of B4B60155. XF-720kw.zip This is bobs1.bin renamed to better reflect it's purpose. I may have jumped the gun here, but I like the provenance of the source and the consistency of the pudding just feels very right. Enjoy. 2 Quote Link to comment Share on other sites More sharing options...
1050 Posted March 1, 2019 Share Posted March 1, 2019 To make it complete then I applied Woolley's density switching to his stock rom and offer it below. X360W.bin 6DEB9082 CRC-32 Checksum-32 0009A299 D438B4D9 original rom CRC-32 Checksum-32 0009AE7E I suspect original sourced from Bob Woolley's post on atariage is the 2nd generation PAL rom, but I can't know for sure until some Europeans weigh in with postive results on their PAL systems. Made by Lee from stock XF-551 rom by applying these changes: $0528 90 to 00 spin-up on FORMAT only. $09af 99 to 24 jump to density switch code ef to e0 and the density switch code $09AF $24,E0 these two bytes are shown twice $09E0 $09,53,08,C6,F0,9A,CF,8A,10,99,E7,24,B1 $09F0 $8A,30,89,08,99,EF,24,B1 X360W.zip 1 Quote Link to comment Share on other sites More sharing options...
hueyjones70 Posted March 20, 2019 Share Posted March 20, 2019 I have been trying to figure out how my 3.5 drive is set and I found three solder points in triangle arrangement two are labeled DS1 & DS2; there is a connector between DS1 and unlabeled point. Is the likely jumper that needs to be changed? Quote Link to comment Share on other sites More sharing options...
+SoulBuster Posted March 20, 2019 Author Share Posted March 20, 2019 Have you tested the drive to see if it works as is. My drive select counts from 0. Yours seems to count from 1 and is already set there. Quote Link to comment Share on other sites More sharing options...
hueyjones70 Posted March 21, 2019 Share Posted March 21, 2019 The drive will not read a disk nor can it be formatted. It appears to be trying to read and format otherwise. Quote Link to comment Share on other sites More sharing options...
hueyjones70 Posted March 21, 2019 Share Posted March 21, 2019 I had a typo error the labels are ds0 and ds1. DS1 appears to be connected. Quote Link to comment Share on other sites More sharing options...
+kheller2 Posted March 21, 2019 Share Posted March 21, 2019 DS0 is correct for systems other than a PC. 1 Quote Link to comment Share on other sites More sharing options...
_The Doctor__ Posted March 21, 2019 Share Posted March 21, 2019 disconnect ds1 and connect ds0 Quote Link to comment Share on other sites More sharing options...
+kheller2 Posted March 21, 2019 Share Posted March 21, 2019 I had a typo error the labels are ds0 and ds1. DS1 appears to be connected. That doesn’t make sense. The drive would not respond at all if this was set wrong. Unless a cable is twisted or something else is goin on. Quote Link to comment Share on other sites More sharing options...
+SoulBuster Posted March 21, 2019 Author Share Posted March 21, 2019 if your cable has a twist in it like this and it is between your drive and PCB, DS1 is the correct setting. If the cable is all flat, you need to change the drive from DS1 to DS0. Quote Link to comment Share on other sites More sharing options...
+kheller2 Posted March 21, 2019 Share Posted March 21, 2019 if your cable has a twist in it like this and it is between your drive and PCB, DS1 is the correct setting. If the cable is all flat, you need to change the drive from DS1 to DS0. 41ZP5QTXRBL.jpg That almost sounds right... but I don't think it is. The XF uses pin 16 (motor) and 10 (DS0) PC's use 10 (Motor A) , 12 (DS B ), 14 (DS A), 16 (Motor B) So when 16 and 10 are HIGH, you have Motor A and Motor B but no DS. AFAIK, the only way to get the drive to respond is setting it to DS0 OR creating your own twist jumping ping 10 to wire 14. I think. Not enough coffee yet and I'm sure someone smarter than I will correct this. Quote Link to comment Share on other sites More sharing options...
hueyjones70 Posted March 21, 2019 Share Posted March 21, 2019 I have two 3.5 drive mechs that I have tried connect to a XF551 PCB. One of the mechs has a slider switch on the side the other has nothing that I can see, when the slider is set to 0 and the PCB switch is set to drive 2, the drive seems to be attempting to respond. If I attempt to read or format the 3.5, it spins up makes some slow beeps and eventually gives an error 144. The disk is not HD. The only thing I can think that might be a problem is the flat cable. The PCB worked with a 5.25 drive and I am using a hyper version B chip. Looking for suggestions. Both mechs exip the same behavior. Quote Link to comment Share on other sites More sharing options...
+kheller2 Posted March 21, 2019 Share Posted March 21, 2019 I have two 3.5 drive mechs that I have tried connect to a XF551 PCB. One of the mechs has a slider switch on the side the other has nothing that I can see, when the slider is set to 0 and the PCB switch is set to drive 2, the drive seems to be attempting to respond. If I attempt to read or format the 3.5, it spins up makes some slow beeps and eventually gives an error 144. The disk is not HD. The only thing I can think that might be a problem is the flat cable. The PCB worked with a 5.25 drive and I am using a hyper version B chip. Looking for suggestions. Both mechs exip the same behavior. Did you try the PCB with the 5.25 and version A? And what WD chip is in there? Quote Link to comment Share on other sites More sharing options...
hueyjones70 Posted March 21, 2019 Share Posted March 21, 2019 When I used the PCB with a 5.25 I had the stock IC (101696??)and a WD1772. Quote Link to comment Share on other sites More sharing options...
hueyjones70 Posted March 21, 2019 Share Posted March 21, 2019 I wonder about the cable because it is a homebrew. I may go pack and recheck the PCB with a 5.25 I am leary of doing much with the PCB because of its inherent fragility. Quote Link to comment Share on other sites More sharing options...
Kyle22 Posted March 22, 2019 Share Posted March 22, 2019 I guess the 144 means that it's done. Quote Link to comment Share on other sites More sharing options...
hueyjones70 Posted March 27, 2019 Share Posted March 27, 2019 Should the 3.5 drive work with any DOS or does it have to be a specific DOS like SPARTADOS? I have done everything that the instructions say to do and I am using the HYPEROM B, I have tried 3 different 3.5 drives and none of them will work. The drives come on and spin up, the computer gives a few beeps and then I get an error 144 or error 163. Quote Link to comment Share on other sites More sharing options...
_The Doctor__ Posted March 28, 2019 Share Posted March 28, 2019 sparta, mydos, etc there's a few that should do it... 1 Quote Link to comment Share on other sites More sharing options...
+kheller2 Posted March 28, 2019 Share Posted March 28, 2019 Just to be clear, this exact same board works with a 360k mech and the XFA rom? Quote Link to comment Share on other sites More sharing options...
hueyjones70 Posted March 28, 2019 Share Posted March 28, 2019 The board works with a 5.25 using the hyper a rom yes.The cable I am using has the connector for either size floppy. I don't know about the drive settings because I really don't know what I am looking for. Quote Link to comment Share on other sites More sharing options...
Dropcheck Posted March 28, 2019 Share Posted March 28, 2019 If this exact same board works with a 360K mech and the XFA rom and WD1772PH chip...... then the issue is with the data cable, XFB rom, drive or on drive id settings. If you want to assume that the XFB rom is good, then the next step is troubleshooting the data cable to verify you have continuity along all pins at all cable connectors. If the data cable has a twist between the drive connectors that will control what the drive id settings should be on the drive itself. Otherwise the drive id should be set to D0. If the drive you are using is a 1.44M floppy drive I have heard that some require you to flip the cable connector when inserting. What are the make and model # of the drives you are using? Quote Link to comment Share on other sites More sharing options...
hueyjones70 Posted March 28, 2019 Share Posted March 28, 2019 When everything works correctly, can the 3.5 drive be used as drive 1-4 by changing the 551 drive dip switch? 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.