Comments (4)
Similar to #358 the problem is that this IPF does not report the location of the write splice (reported as -1 which means unknown). Greaseweazle currently takes -1 literally, as one bitcell before the index. Unfortunately this IPF reports data across the index, so placing the write splice at the index places it in the middle of that data.
It would be nice if SugarConvDsk could tell us the write splice location but, in absence of that, heuristics similar to #358 will be required. That is, place the splice in a weak area, or end of an NFA, or in a sector gap. In that order.
from greaseweazle.
Is this specific to the example IPF, or generally true for all IPF generated by SugarConvDsk?
Are the verification error(s) on specific track(s), or can errors occur randomly on any track?
from greaseweazle.
Actually, I can't produce myself other IPF with SugarConvDSK, since this software doesn't want to build on macOS.
Paco didn't provide other examples...
The errors occur on random tracks. Example 1:
gw write /Users/yserra/Downloads/RIT.ipf
IPF Image File:
SPS ID: 0000 (rev 1)
Platform: Amstrad CPC
Created: 0/0/0 00:00:00
Cyls: 0-41 Heads: 0-1
Writing c=0-81:h=0-1
T0.0: Writing Track (Flux: 200.0ms period, 219.9 ms total, Terminate at index)
T0.0: Writing Track (Verify Failure: Retry #1)
T1.0: Writing Track (Flux: 200.0ms period, 220.0 ms total, Terminate at index)
T2.0: Writing Track (Flux: 200.0ms period, 219.9 ms total, Terminate at index)
T3.0: Writing Track (Flux: 200.0ms period, 219.9 ms total, Terminate at index)
T3.0: Writing Track (Verify Failure: Retry #1)
T3.0: Writing Track (Verify Failure: Retry #2)
T3.0: Writing Track (Verify Failure: Retry #3)
** FATAL ERROR:
Failed to verify Track 3.0
Example 2:
gw write /Users/yserra/Downloads/RIT.ipf
IPF Image File:
SPS ID: 0000 (rev 1)
Platform: Amstrad CPC
Created: 0/0/0 00:00:00
Cyls: 0-41 Heads: 0-1
Writing c=0-81:h=0-1
T0.0: Writing Track (Flux: 200.0ms period, 219.9 ms total, Terminate at index)
T0.0: Writing Track (Verify Failure: Retry #1)
T1.0: Writing Track (Flux: 200.0ms period, 220.0 ms total, Terminate at index)
T2.0: Writing Track (Flux: 200.0ms period, 219.9 ms total, Terminate at index)
T2.0: Writing Track (Verify Failure: Retry #1)
T2.0: Writing Track (Verify Failure: Retry #2)
T3.0: Writing Track (Flux: 200.0ms period, 219.9 ms total, Terminate at index)
T4.0: Writing Track (Flux: 200.0ms period, 219.9 ms total, Terminate at index)
T4.0: Writing Track (Verify Failure: Retry #1)
T4.0: Writing Track (Verify Failure: Retry #2)
T4.0: Writing Track (Verify Failure: Retry #3)
** FATAL ERROR:
Failed to verify Track 4.0
The above examples were tried with the same floppy disk, which works for any other writing.
To rule out any possible problems with the 3" drive, these examples were carried out with a 3.5" drive, on a 3.5" floppy disk.
from greaseweazle.
Here's probably another one, from Paco Gonzalez, Knight Force:
from greaseweazle.
Related Issues (20)
- 8" Floppy: extra empty tracks in the image HOT 3
- PC disk types HOT 1
- Non-zero-indexed track numbers not handled correctly HOT 6
- Is a Blue Pill definitely fake if it fails Blinky? HOT 17
- NoIndex HOT 18
- Need help reading 5 1/4" Monkey Island 1 360k floppies HOT 1
- gw seems to ignore rpm= when writing to 5.25HD diskette HOT 8
- Add syzygy diskdefs for TRS-80 M1 HOT 6
- Redefinition of _FORTIFY_SOURCE HOT 2
- error: externally-managed-environment HOT 8
- OS9 Configuration HOT 6
- 5.25 loppy drives with density pin HOT 5
- How can I get gw to honor rpm= in diskdefs when writing? HOT 2
- greaseweazle-1.17-win64.zip has a virus HOT 2
- Unable to use --adjust-speed parameter with Apple II formats HOT 2
- Trackloading or custom loading fails in WinUAE HOT 1
- Apple II raw images created with Greaseweazle do not read properly in other applications HOT 5
- Dead/Bad Greaseweazle? Pins 10,34 shorted to ground. Unable to read disks. HOT 7
- Commodore 1541 format: 40 vs 35 tracks HOT 4
- Best practice for reading 800k Mac disks and converting to disk image files? HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from greaseweazle.