Posts that appear to be low-effort and not adding anything useful to the subreddit may be removed, and repeated warnings may incur a ban from posting While it's a bit of a touchy subject linking to downloads for older software will generally be allowed to stay, unless it's blatantly outright piracy and or a DMCA is received Question is too low level and must be related to how electronics/architecture works).While the sub name is Windows 98, anything 9x related is alright, there's no issue in posting content related to 95, 98, 2000 or MEīe civil in the comments, if you're being outright obnoxious the comment has a good chance of being deleted and you getting a warning or temp/permanent ban depending on history (Not sure if EE is correct place to put this question to however stackoverflow seems to be less proper, serverfault is also non-fit. ![]() I suspect there must be something else, but I can not figure out what it might be. But here driver is unable to read even sector 1 at head 0 track 0 (boot sector) to identify the geometry. ![]() My assumption was that I just *2 track number, at least it must yield correct reading of data. I have problems finding information on how to support older 360k formats on newer drives. The same custom driver works properly with 3.5" drives' 1.44M and 720k formats, and with 5.25" drive's 1.2M format, only 360k is having problems. The FDC speed set is 250 kb/s (CR1=1, CR0=0). Here's what I send to controller: 46 00 00 00 01 02 01 2A FFĪnd here's what I get in response 40 01 00 00 00 01 02 ![]() The controller returns "address mark not found". I am using the same drive to read data from 360k diskette back using custom driver. I formatted several 5.25" diskettes with 360k and 1.2M on the Windows XP PC using 1.2M (HD) drive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |