Did you change something to your Windows? A recent Windows update?
There is also nothing wrong for recommending to a user to upgrade to the last version of a software…
No changes. Walked away 30 minutes for coffee. Returned and could not remember if did a full build, so clicked full build and error appeared.
I know there is nothing wrong with you recommending to upgrade. But, put yourself in my shoes. I have a project to complete, get that error and support says try software upgrade to solve when current version been working on same project for two weeks.
Anyway, appreciate your input. Got a solution for now to complete project.
Sure, but something got wrong obviously. If restarting the computer doesn’t help, check if some software isn’t interfering. Turning antivirus program off. Check if there is no other PBuilder.exe process in memory when you get the error.
Was a resolution ever found for the error? I have upgraded to the latest version and reboot my devices several times. I have also uninstalled and reinstalled. Any other suggestions?
Package Summary:
Description: Paquet Archive - StartSC.exe
EXE Format: 32-bit EXE (x86)
Type of package: Package for general file distribution - IDStandard
Author: Randy Hastings
Date/Time: 4/27/2018 2:56:30 PM
Checking Settings
Listing files to be compressed…
Analysing user settings…
Selected unpacking engine: Small
Output Directory: C:\Users\rhastings\Desktop
Settings checked; the compilation can continue.
Building Package Stub
Writing resource string table…
–> COMPILATION ERROR <–
A fatal error has occurred:
Compilation Failed for Script "C:\Users\rhastings\Desktop\bin\mainscript.c
Compilation aborted; The package has NOT been created.
Make sure you installed PB on a hard disk and you access it not from a network share folder. That could explain why the virtual “pbcore.h” file is not accessible.
I got the fatal error failed … on pbcore.h
I tried reinstalling and that does an uninstall first, but not luck.
I then used Windows Programs and Features and uninstalled PB first. Then I reinstalled and now it is fine. All of my project files were still referenced and I selected Recently Used from the opening screen and they were all there. Seems OK now.
So, if we do not pay to get the “hot fix”, can no longer use paquet builder with Windows 10?
Hope that is not he case, as issues like this should be covered. It is not the ends users fault that the software is no longer compatible with Windows 10 platform…
Cannot use at all for any project. Paquet Builder no longer works on Windows 10 at all for me. Cannot change/update any past projects. Really bad business.
The hot fix (PB 3.7.1) was available for all PB 3.7 users, even those with a maintenance that expired between 3.7 and 3.7.1. But it is an exception, we don’t provide updates to end users without maintenance anymore. And our providers do the same.