-
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Unsupported 16-Bit Application #5
Comments
Never seen that one! Hmm, which windows version are you in? |
We are in Windows 10 company-wide (and I checked that specific machine just to be sure.) |
K, so I just made an update that I think fixes it as I was using an older windows API codepack for something, Can you try the latest installer here: |
Great! I'll get back to you - I need to get with one of our IT crew w/admin privileges once they are available. Thanks John! |
The new installer worked great. Thanks again! Another question: does the add in fetch the same packages per each version of Revit? I had initially set up my pull location to contain a folder for each Dynamo version (2.6, 2.12 2.16, etc), but I'm thinking this is not correct? |
At this time, it’s one location to all versions. But you can modify the ini
that gets installed in programdata.
C:/ProgramData/Autodesk/Revit/addins/2021/fetch
…On Thu, Apr 13, 2023 at 12:29 PM pinkrick83 ***@***.***> wrote:
The new installer worked great. Thanks again! Another question: does the
add in fetch the same packages per each version of Revit? I had initially
set up my pull location to contain a folder for each Dynamo version (2.6,
2.12 2.16, etc), but I'm thinking this is not correct?
—
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADYD5VAUIEJ2JANR7VATLKLXBBAZ7ANCNFSM6AAAAAAWVUWWMI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
We recently saw the below warning when attempting to run the installer on one of our machines. Is this a known issue?
The text was updated successfully, but these errors were encountered: