InCD and System Restore in WinXP

[talidyce]

Hello folks!
I've managed to get InCd working by following the steps described in: http://www.cdrlabs.com/phpBB/viewtopic.php?t=9572
To keep the modified drivers at bay, I had to disable system restore. Now this is not the ideal condition as this protection is removed, would any unfortunate corruption occur to the system.
I just could not find how to get around this issue so I had to ask: what am I missing?
Using InCd 4010.
Any help greatly appreciated.

[UALOneKPlus]

Advice - don't use InCD, or CD-RW technology.

You'll thank me later.

[CDRecorder]

You could try updating to InCD 4.0.1.21, but in my opinion, I wouldn't use InCD 4 until certain bugs have been repaired.

[Mattias]

UALOneKPlus: Why don't you think we should use the CD-RW technology (or InCD)?

[Bhairav]

Mattias, that is probably because those 2 programs can cause a lot of headaches, with conflicts with other programs and being buggy.

[UALOneKPlus]

UALOneKPlus: Why don't you think we should use the CD-RW technology (or InCD)?

CD-RW's are super unreliable.

I've used both DirectCD and InCD, with terrible results. Valuable data on CD-RW's started getting lost, because my PC all of a sudden was unable to read some of the CD-RW's that were only a few weeks or months old. Fortunately I never trusted CD-RW's to begin with, so I always burned the data to CD-R's as well.

IMHO, CD-RW's are not ready for public usage, and really should be considered a highly unreliable and risky technology for temporary storage.

[CDRecorder]

I haven't found the CD-RW discs themselves to be reliable as long as I used a decent drive. In my experience, the best drives for CD-RW recording have been my Lite-Ons.

On the other hand, packet-writing software has sometimes been unreliable. I have usually had pretty good luck with DirectCD, though.

[talidyce]

Hey folks,
my question was how to get system restore working whilst using InCD. Can anyone help with this please?
I'm using LiteOn and they appear to work quite well (when there are no software conflicts ie Win98).
Thanks for helping!

[CDRecorder]

Well, the first thing I would suggest is updating to the latest version of InCD (according to your previous post, you are using an old version).

[cfitz]

I don't use XP, so I can't offer much advice, but I think if you have disabled system restore you have already lost all your previous restore points. Thus, my guess would be that if you now re-enable system restore, it will take your current configuration, including the drivers you are happy with, as the baseline, and it won't try to overwrite the drivers you are now using.

Maybe an XP expert can help out better...

cfitz

[CDRecorder]

I wouldn't call myself an expert, but you are absolutely right, cfitz!

[talidyce]

Not quite right.
I did re-enable system restore and it re-created the offending dlls that mess up InCD. It took me a little while to figure out why InCD all of a sudden stopped working. Re-disabled system restore, re-cleaned up the dlls, et voila!. Didn't dare re-enabling SR again and that when I came up here for a possible solution.
I did upgrade to the latest version, but it didn't make a difference.

[Inertia]

talidyce,

It would be helpful if you would provide specific details about the following:

1. Driver modifications you have made.

2. The "offending" DLLs that system restoring is recreating.

Version 4xx of InCD is much less reliable than v3.52.40.

[dburg]

Version 4 of InCD is mostly statically linked against dlls except its own incdapi.dll, drivelocker.dll and system-core dlls. Thus I do not understand how they could be a mess with dll. What is it exactly: the installer overwrite them, or InCd doesn't work as long as you do not manually change some dlls?

[talidyce]

Hello all,
here are the files I had to modify to get InCD working (not sure exactly which ones are the direct offenders, couldn't afford testing them individually): CD20XRNT.SYS, CDAUDIO.SYS, CDFS.SYS, CDROM.SYS, UDFS.SYS, CDFVIEW.DLL, CDM.DLL, CDMODEM.DLL, CDOSYS.DLL, UDHISAPI.DLL, CDR4DLL.DLL, CDRAL.DLL, CDRTC.DLL.
These get re-created if I re-enable SR and the machine goes crazy.
When I first assembled the machine with the LiteOn 52x24x52, I installed the bundled Nero that came along. Rebooted no problems. Installed InCD v3.xx ==> BSOD. Computer restarts by itself 2 or 3 times No go. I then went through the cleansing procedure outlined at cdrlabs topic 9572, disabled SR (just in case), still no go. D/loaded V4.0.x installed et voila! It's working. On re-enabling SR, the saga re-starts. Checked again for the above files and found that yes, they had been re-instated. Disable SR, cleanup ==> fine.
As some pple here suggested I tried going back to version 3, tried 4 different flavours of them (using nero cleaner and JV16T in between + manual mopping), as soon as the InCD splash screen at bootup appears ==>BSOD with a message: Driver_IRQ_NOT_LESS_OR_EQUAL. The technical blurb at the foot of the message gives some kind of memory addressing issue: xxxSTOP: 0x000000D1 (0xF8BFC000, 0x00000007, 0x00000000, 0xF847DC02) some of these changed on occasions.
The PC also has a LiteOn CDROM, so I install EWReader to enable access to RWs. The CDROM drive stopped accepting CDRs and would only read CDRWs! UH!! Removed EWReader ==> CDROM back to normal.
The machine spec:
Mobo: Soltek SL-75FRN-L with nVidia Chipset
CPU: AMD Athlon XP 2000+
HDD: 80 GB Seagate
RAM: 512 DDR 333
CDRW: Liteon 52x24x52
CDROM Liteon 52x
Graphics GeForce4 MX440 SE AGP
OS Win XP Pro (with all SPks + patches loaded)
Long blurb but just tried to give an accurate picture. Please fire any further questions ):

[dburg]

I honestly don't know how system restore deal with registry when restoring a missing driver. The drivers you removed include ISO 9660, UDF filesystem reader, and the cd-rom class driver itself. I do not expect InCD 4 to be able to work properly in such conditions as relies for a part on a filter-driver of the cd-rom class. If the cd-rom class driver is not there, the filter driver cannot load, thus InCD 4 will probably refuse to start.

If disabling SR might be necessary for InCD 3, I would expect that with InCD 4 SR should be kept on, especially, be on before the installation.

[talidyce]

Thanks DBurg for following up,
I did try indeed enabling SR with V4 and had the same issues. Reasons for my posting. With SR ON, it's a no go. I have another machine with Win98SE and had no problems whatsoever. I did perform some drivers cleanup there too to get it trouble-free (different sys and dll).
Do other people successfully use InCD with XP Pro with SR on? I just want to find a way to get it right.

[dburg]

What is the content of the bluescreen? Have you sent the crash-report to Microsoft for analysis?

[talidyce]

BSOD message:
A problem has been detected and Windows has been shut down to prevent damage to your computer.
Driver_IRQ_NOT_LESS_OR_EQUAL
If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:
Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any windows updates you might need.
If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing.
If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Start Up options, and then select Safe Mode.
Technical Information:
xxxSTOP: 0x000000D1 (0xF8BFC000, 0x00000007, 0x00000000, 0xF847DC02).
Another time:
xxxSTOP: 0x000000D1 (0xF8B82000, 0x00000007, 0x00000000, 0xF847DC02).
I was not online so couldn't send a report with the BSOD. On reboot the system did ask to send a report to MS which I denied as I've never heard back from them on other occasions so what's different for this?
When the machine BSODs, I have to push the reset button to resume.
Don't know if the above is of any help as it appears to be a standard BSOD message.
I did disable shadowing options as advised with no improvement.
Thanks for helping.

[dburg]

The purpose of crash report is detailed on Microsoft web site:

http://oca.microsoft.com/en/Welcome.asp

Ahead Software is registered to this program and actively attempts to fix crashes Microsoft engineers forward to us.