Announcement

Collapse
No announcement yet.

Visual C++ Library Error

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • GµårÐïåñ
    replied
    Originally posted by GregiBoy View Post
    Have you ever thought that it may be your installations?

    I've NEVER had a problem and neither have a lot of other users....
    Installation is a generic and vague term. Installation of what? DVDFab? Windows? User/Profile/Registry? Which exactly?

    Also, as I have said before, even if it happens to 1% of the population, its an error and its too much. We can't use the majority rule to excuse issues that are very real.

    Leave a comment:


  • GregiBoy
    replied
    Have you ever thought that it may be your installations?

    I've NEVER had a problem and neither have a lot of other users....

    Leave a comment:


  • GµårÐïåñ
    replied
    Originally posted by bean55 View Post
    Hey Buddy I guess it's time to send off for a new key.
    Already did that when we were told to get new ones for 5, I mean how many times do I have to get a new one to make the program work? I mean the program should respect and properly process the license keys no matter what. I wish they would spend less time screwing with the license routine and actually spend it getting the program to work right.

    I mean it works up to 6.0.6.0 then it doesn't, that's insane and I install on another machine it worked. I tried on another machine it didn't. Its just arbitrary in behavior and that is not right.

    Leave a comment:


  • bean55
    replied
    2. I don't have the original email, just the license in a text file, how I enter its should not matter.
    Hey Buddy I guess it's time to send off for a new key.

    Leave a comment:


  • GµårÐïåñ
    replied
    Originally posted by signals View Post
    Here is what I do, it has never failed me:

    Log on to Windows as Administrator or with Administrator permissions
    Install latest version of DVDFab, then close the program
    Download keyfile (from the email attachment) to desktop
    Disconnect from internet
    Fully disable all AV, spyware, malware etc applications
    Double click on the keyfile attachment on your desktop
    DVDFab should open fully registered, verify in help->about
    1. I am the admin, logged on as such and run everything as such, not the issue.
    2. I don't have the original email, just the license in a text file, how I enter its should not matter.
    3. It is ridiculous, unnecessary and a sign of bad programming to have to disable half your machine to get something to work right, unacceptable.

    Leave a comment:


  • signals
    replied
    Here is what I do, it has never failed me:

    Log on to Windows as Administrator or with Administrator permissions
    Install latest version of DVDFab, then close the program
    Download keyfile (from the email attachment) to desktop
    Disconnect from internet
    Fully disable all AV, spyware, malware etc applications
    Double click on the keyfile attachment on your desktop
    DVDFab should open fully registered, verify in help->about

    Leave a comment:


  • GµårÐïåñ
    replied
    Originally posted by Wild and Blue View Post
    The code you copy and paste is it in a .txt file? if so you can just rename the .txt extension to .DVDFab6 and then double click it as bean55 mentioned or just send for a new ver.6 key since ver.5 keys won't work.
    Mine was in an email and I do cut and paste. Currently its kept in a text file. However, renaming and running doesn't work, it says invalid, so maybe there is more to a .dvdfab file. Or its a escape character causing an issue like char(0) or (13) otherwise known as Cr/Lf.

    As for validity, I am sure its a valid 6.x license, since it has been working since 6.x has been used, so pretty sure that's not it. I have done everything I can think of and all of what has been written by friends like SJ to try and fix it by cleaning house on this machine but I can't think of anything else and its not working. Like something is not right and I don't get what. ARGH!

    Leave a comment:


  • W&B
    replied
    No buddy because mine is from a while back where you cut and paste.
    The code you copy and paste is it in a .txt file? if so you can just rename the .txt extension to .DVDFab6 and then double click it as bean55 mentioned or just send for a new ver.6 key since ver.5 keys won't work.

    Leave a comment:


  • GµårÐïåñ
    replied
    Originally posted by bean55 View Post
    Not sure buddy, but the last couple clean installs that I done I kept the program closed, double clicked the reg key and then started DVDFab and everything was good, no more trial user.
    I guess I need to figure out how to get my code in the same way so I can do that too and see if it makes a difference. The problem is that it shouldn't or once again it brings to the program being done poorly or it should make ZERO difference how you do it.

    Leave a comment:


  • bean55
    replied
    Not sure buddy, but the last couple clean installs that I done I kept the program closed, double clicked the reg key and then started DVDFab and everything was good, no more trial user.

    Leave a comment:


  • GµårÐïåñ
    replied
    Originally posted by bean55 View Post
    Guardian are you double clicking the reg key with the program closed?
    Seems to work better that way.
    No buddy because mine is from a while back where you cut and paste. You think something is wrong with the code? why now, why work fine up to 6.0.6.0 and then suddenly take a crap on 6.0.7.0 and start doing it by giving a library error first? Makes no sense.

    I just installed on another machine and used the same code and it worked just fine and its up and running, so what gives?

    Leave a comment:


  • bean55
    replied
    Guardian are you double clicking the reg key with the program closed?
    Seems to work better that way.

    Leave a comment:


  • GµårÐïåñ
    replied
    Originally posted by toaddub View Post
    @GµårÐïåñ,

    Are you saying 6.0.6.0 without VSO burning engine installed successfully, but 6.0.7.0 doesn't? Try again with the VSO engine deselected. But I don't think it's the VSO engine that's causing the problem. It's the installation script. DvdFab is programmed in VC++, maybe it's from 2008 or 2005 package, but judging from the GUI, it's probably 2008.

    Check that you have Microsoft Visual C++ 2008 (and/or 2005) SP1 Redistributable Package installed in Add Remove Programs.

    VSO burning engine uses SPTI if you're running under admin account and Patin-Couffin if you're running under user account.
    I don't deselect anything, the installer doesn't give that option, at least not that I have seen. The 6.0.6.0 installs with the VSO and runs fine. Then 6.0.7.0 gives this error and in the options there is no VSO. Then I reinstalled it clean and now no more VC++ errors but now the DVD-DVD option is missing from options, including VSO and for some odd reason now it tells me that I am a trial user. I have re-entered the registration information and it takes it, restarts and goes back to trial again.

    Leave a comment:


  • GµårÐïåñ
    replied
    Originally posted by 90312 View Post
    Hey Guardian! I’m about to throw in the towel on this one, but have one more question. Are you by chance running WoW on those machines? My grandson catches this error once in a great while after a major patch. Somehow it corrupts a protected system file. I run sfc on his laptop and the file is replaced and it’s all good. The last time a virus sneaked by his AV program I think it was Win32/Pirate or something like that anyway it had the same affect even after removal. You’ve probably already done this but for others that this might work for: open a command window and type sfc /scannow
    Ahhh hell no, I have nothing against it but no time for anything like that. These machines are pretty minimalistic and straight to function only. But I ran the AV just the same, 3 engines and nothing dirty on this machine.

    Leave a comment:


  • GµårÐïåñ
    replied
    Originally posted by Wild and Blue View Post
    Mentioning corrupt installers, when 6069 was released I d/led and went to install but got an error pertaining to just that, 1st time I ever had to re-d/l an installer. might be something to check out. Just thought I'd mention it
    Agreed, I have never had any corrupt installers either. I am not even sure that's the problem here now that its giving new inventive issue.

    Leave a comment:

Working...
X