SEND TO VETUS = OK, SAVE TO VETUS = ISSUES

Midwest Mac · 2026-03-30T00:43:26Z

I have a good sized .chip file that is a work-in-progress that I can get to SEND TO successfully and run (or at least appears to, hunting down a logic error in the code), but when I SAVE TO, VetusGUI returns that it completed the save successfully way to soon. First I was thinking Vetus hardware was being efficient and saving the SEND TO version since there were no changes... However, the test does not show in the menu on the hardware. When I REFRESH to pull the current list, there is a blank file at the bottom of the list in VetusGUI. If I load that from the hardware into VetusGUI, I will get either the correct Code, Chip Name, Num Pins, Chip Type, and Image fields but the String# fields will all be empty or have invalid characters in them - OR - I will get nothing. A full reboot of the hardware, close/open of VetusGUI and doing a direct SAVE TO results in the same type of behavior. I'm on Windows 11, I have updated the hardware to 1.0.3. I have other much smaller test chip files that saved and run without issue.

Page 2 / 2 Prev

Vetus Pars Help

Last Post by NIVBOT 1 month ago

7 Posts

3 Users

0 Reactions

957 Views

RSS

Posts: 8

arnljot

Customer

Jun 25, 2026 12:28 am

(@arnljot)

Active Member

Joined: 1 month ago

PS: I get this behaviour regardless of how many lines of code my test has. 55 or 119, they all need the workaround to get onto the Vetus.

Page 2 / 2 Prev

4 Forums
33 Topics
194 Posts
1 Online
63 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed

Forum

SEND TO VETUS = OK, SAVE TO VETUS = ISSUES

About us

Support

Resources

Get In Touch