Scott James

It sounds like the drives themselves are functioning properly since blanking works and the OEM software can successfully write data. The issue may be related to compatibility between InfraRecorder and older hardware or firmware, especially with rewritable media. You could try lowering the write speed, updating the drive firmware, or disabling the verification step temporarily to see if the burn completes correctly. Sometimes older CD/DVD drives behave inconsistently with third-party burning software....

It’s interesting to see discussions like this around InfraRecorder, especially since it’s still recognized as a lightweight and straightforward CD/DVD burning tool for Windows despite being quite old. From what I’ve seen, many users appreciate its simplicity and ability to handle basic tasks like creating ISO images or burning discs without unnecessary complexity . That said, compatibility with newer systems and hardware can sometimes be a concern due to limited updates. For users who prefer modern...

It’s interesting to see discussions like this around InfraRecorder, especially since it’s still recognized as a lightweight and straightforward CD/DVD burning tool for Windows despite being quite old. From what I’ve seen, many users appreciate its simplicity and ability to handle basic tasks like creating ISO images or burning discs without unnecessary complexity . That said, compatibility with newer systems and hardware can sometimes be a concern due to limited updates. For users who prefer modern...

Thanks for providing those details—that’s really helpful for troubleshooting. Since the splash screen appears briefly before the process exits and crash dumps are being generated, it does point to a startup-level issue rather than a logging or configuration problem. Attaching the crash dump is definitely the right step, as it should give developers more insight into what’s failing at launch. Approaching this systematically—checking dependencies, compatibility, and crash data with the same structured...

Thanks for providing those details—that’s really helpful for troubleshooting. Since the splash screen appears briefly before the process exits and crash dumps are being generated, it does point to a startup-level issue rather than a logging or configuration problem. Attaching the crash dump is definitely the right step, as it should give developers more insight into what’s failing at launch. Approaching this systematically—checking dependencies, compatibility, and crash data with the same structured...

This behavior is consistent with how some older Windows 98 applications handle background processes. If Devcpp.exe continues running after the main window is closed, it can prevent the OS from completing shutdown properly, which explains the system hang you’re seeing. Manually ending the process via Ctrl+Alt+Del is a workable temporary solution, but a more stable fix would be to disable any Dev-C++ background tasks, check for known compatibility issues with Win98, or use an older/lighter build that...

This behavior is consistent with how some older Windows 98 applications handle background processes. If Devcpp.exe continues running after the main window is closed, it can prevent the OS from completing shutdown properly, which explains the system hang you’re seeing. Manually ending the process via Ctrl+Alt+Del is a workable temporary solution, but a more stable fix would be to disable any Dev-C++ background tasks, check for known compatibility issues with Win98, or use an older/lighter build that...

As someone who’s been exploring TurboCASH, I really appreciate how this project offers a simple yet powerful open-source accounting solution for small businesses and solo entrepreneurs—it covers everything from general ledger and invoicing to multi-language support, and the community around it is genuinely helpful. The Wiki gives a clear snapshot of its features and potential, and I think with more user contributions it could become even more complete. On a lighter note, while I was taking a break...