Re: Batch Ripper and external loader commands
Ok. Thanks, that helps.
I'm working out some issues with Jason regarding IDE drive access (trays on connected-via-IDE PX-708 drives were only opening halfway, etc. with the current ULCLI drivers, when there wasn't a problem over USB/Firewire which I've done 90% of my testing with).
For now, I've added a switch to bypass my own SPTI calls and use some more everyday calls instead...that seems to have worked for him, but you give up a bit of throughput if you uses that flag (better than a stopped process though!).
In the future, I might try to either grab an exclusive (non-shared) write handle to the device for SPTI use before using SPTI calls...or fall through to non-SPTI calls if the handle-request fails (which I suspect it will if you have a handle open).
EDIT: there's also a chance that my SPTI calls are in some way malformed from the perspective of a raw ATAPI device (one that isn't bridged via another protocol...) or at least a raw ATAPI PX-708 device.
I don't have any PX-708s to test here, but the workaround I gave to Jason lowers the issue priority for me.
Thanks again.
-brendan
Ok. Thanks, that helps.
I'm working out some issues with Jason regarding IDE drive access (trays on connected-via-IDE PX-708 drives were only opening halfway, etc. with the current ULCLI drivers, when there wasn't a problem over USB/Firewire which I've done 90% of my testing with).
For now, I've added a switch to bypass my own SPTI calls and use some more everyday calls instead...that seems to have worked for him, but you give up a bit of throughput if you uses that flag (better than a stopped process though!).
In the future, I might try to either grab an exclusive (non-shared) write handle to the device for SPTI use before using SPTI calls...or fall through to non-SPTI calls if the handle-request fails (which I suspect it will if you have a handle open).
EDIT: there's also a chance that my SPTI calls are in some way malformed from the perspective of a raw ATAPI device (one that isn't bridged via another protocol...) or at least a raw ATAPI PX-708 device.
I don't have any PX-708s to test here, but the workaround I gave to Jason lowers the issue priority for me.
Thanks again.
-brendan
Comment