Crashes on Start up

[Pete Mazz]

Hasn't worked since 8022 (still working). Crashes when it tries to start. Get the dialog to send report. Sent report (several). Got responses from you to do a clean install, etc. Still have the problem and no one is responding.

Please advise.

[Mona]

Hi Pete Mazz,

Did you try to uninstall and reinstall DVDFab in safe mode?
If not, please start your computer on safe mode to uninstall DVDFab 8 again, then install the latest version 8.0.5.6 of DVDFab at to see the result.

Thanks.

mona

[Pete Mazz]

That didn't work either. Crashes immediately.

Went back to 8.0.2.2

[W&B]

Try manually deleting the DVDfab folder in the appdata folder.

[Pete Mazz]

That didn't work either. Back to 8022....

Got another response via email. They're trying to figure it out.

[maineman]

Hi Pete,

Sorry for your trouble.
Not sure what you've tried besides what's in this thread, but...

Recommend uninstalling using the Fab uninstaller.
Run
Run the Windows Cleaner and be certain to
tick the Old Prefetch data.

Now run the Application Cleaner.

Do a search and manually delete anything to do with Fab if there are files, fragments leftover.

This maybe be overkill, (but it won't hurt anything) but in
device manager, scroll down to VSO, click + to expand and
delete all instances of patin-couffin driver
(pc driver will reinstall with a new Fab install anyway as long as you don't deselect VSO upon install.
Honestly, you don't need it since VSO uses SPTI now and Img is a better burn engine).

Now run the CCleaner Registry utliity.

Reboot, and get a fresh download of Fab and install.
You will also have to re-activate the program.
Personally, I'd go the the DVDFab.com site > Members
and download a new regkey
(Might as well start fresh with everything as long as you've gone this far)

Hope this helps and again, sorry for your trouble, but at this point, it's what I'd do.

[Pete Mazz]

No dice. Installed 8022 w/o even uninstalling 8056 and it works like a champ. Very strange.

[90312]

Another user had a similar problem then he discovered he had his BluRay drive assigned to B:, he assigned it to another letter D: thru Z: and it worked for him. You don't by chance have an optical drive assigned to A: or B: do you?

[sunny]

Hi Pete Mazz,

Could you post the crash report here for our devs to check and figure out a solution for you? Thanks for your valuable time and patience.

Best regards,
--
Sunny
________

[Pete Mazz]

Another user had a similar problem then he discovered he had his BluRay drive assigned to B:, he assigned it to another letter D: thru Z: and it worked for him. You don't by chance have an optical drive assigned to A: or B: do you?

Wow! That was it. Never had a problem before but that fixed it. I wasn't even using the B drive (BDROM), I was just ripping my DVD collection to my server from another drive.

Many thanks to all!!

Pete

[IVaN_000]

Another user had a similar problem then he discovered he had his BluRay drive assigned to B:, he assigned it to another letter D: thru Z: and it worked for him. You don't by chance have an optical drive assigned to A: or B: do you?

OMFG! Thank you so much. I didn't know what else to try. I feel happy and frustrated at the same time.

It actually makes sense to set the old forgotten B: letter to the BD drive. (Anyone in this forum remembers the old big 5 1/4 floppy drives?)

[90312]

Sure thing, and my first computer used single side 5 1/4 inch flopy disks they held a whopping 180mb. Yeah I remember them.

[maineman]

(Anyone in this forum remembers the old big 5 1/4 floppy drives?)

Yup...
Remember having to hassle with Windows 3.1 HIMEM.SYS so you could play cool games like Wing Commander?...lol

Glad to hear you're up and running smoothly

[90312]

Yup...
Remember having to hassle with Windows 3.1 HIMEM.SYS so you could play cool games like Wing Commander?...lol

Glad to hear you're up and running smoothly

And sometimes you had to set
files=30 and
buffers=30 to run the really cool games.

[GregiBoy]

I remember the 8" disks !!!