i/o error 103 during demux

[gft]

I tried searching the forums to no avail.

When dvd2svcd tries to demux its big mpg file (multiplexed with bbmpeg) I get this error:

- 12/08/2002 10:55:44 PM
- Free on drive E: 1887.12 mb
- Demuxing
--------------------------------------------------------
Demuxing: E:\encode\bbMPEG_Muxed_File00.mpg
I/O error 103

I'm running the latest version in windows 2000. Does anybody have any idea how to fix this?

If not, can I demux myself and then have dvd2svcd finish the rest on its own? I tried demuxing myself and adding the necessary entry into the log to make dvd2svcd think it had already finished demuxing, but when recovering from the SVCD Authoring point it would always try to demux again, with the same error.

More importantly (as I can do the authoring myself if I have to) - how can I prevent this error in the future. I would rather dvd2svcd be able to do the entire process.

Also, it would be nice if dvd2svcd could make the i-author .vpj file on demand, because I am having to finish this svcd by myself, and I don't know how to add chapters (and I shouldn't have to do this myself; dvd2svcd should do it ^_^ ).

The same mpg file is demultiplexed by TMPGEnc with no errors.

Thanks,
gft

[UltimateDBZ]

This may or may not be a source of your problem, but either way, you should really get either a larger hard drive or another one altogether. Having anything less than 10gb free on Windows creates a bottleneck and can leave applications very unhappy as they fight for the remaining space, not to mention Windows' over-aggressive cache. You can pick up a decent 40gb 7200 rpm drive for $75-ish.

[gerti67]

Hi gft,

would you please :logfile: - the complete one.

Greetz,
Gerti

[gft]

I'm quite sure 10 gb is fine for a non-system disc. Seeing as I've done other, similar dvd2svcd projects with less space free, I don't think that should be an issue.

Anyway, I scrapped the project and am coming back to it later - hopefully it's just a fluke and won't happen again.

I'll post another reply if I get the error again - with my full logfile ^_^

Thanks,
gft