VCC crashes with command line BIN parameter about vcc HOT 6 CLOSED

On Sat, Oct 28, 2023, 3:05 AM Ting Tron ***@***.***> wrote: When Vcc.exe is executed with a command line parameter for a BIN file, most of the time - the Vcc application does not appear - it turns out it crashes after 2-4 seconds. However, once every 8-10 times, it runs the BIN program successfully. I tried various ways of executing with the same behavior: - directly in Windows Command Line or from a different batch file or "shell" - using Run as Administrator - from within the VCC folder and from another folder - with or without any combination of carts and disks: with/without MPI cart, or with/without a disk, even with a disk having the same BIN file - with or without CPU over-clocking When executed, the Task Manager shows two new copies of the VCC process with the same BIN argument, even though in all the methods of launching, only one launch was performed. Their Status changes from Running to Suspended and then they vanish one after another within about 2-4 seconds. [image: image] <https://user-images.githubusercontent.com/2383820/278796304-4991c31f-6479-464b-835e-1d8fc5077b89.png> Event Viewer reports mostly the following issues: Faulting application name: Vcc.exe, version: 2.1.0.8, time stamp: 0x64c0d047 Faulting module name: Vcc.exe, version: 2.1.0.8, time stamp: 0x64c0d047 Exception code: 0xc0000005 Fault offset: 0x00019f40 Faulting process id: 0x0xC388 Faulting application start time: 0x0x1DA0962C72DC383 Faulting application path: c:\embed\Tandy\VCC\Vcc.exe or very rarely Fault offset: 0x000c4ea6 The BIN file is compiled with LWASM with a proper EXEC post-amble start address. So it run without a problem from a disk LOADM"SAMP1" : EXEC SAMP1.ASM: 00050 ORG $1200 00060 BEGIN JMP START 00070 FDB DONE-BEGIN 00100 START LDA #$F9 00110 LDX #$400 00120 SCREEN STA ,X+ 00130 CMPX #$600 00140 BNE SCREEN 00150 WAIT JSR [$A000] 00160 BEQ WAIT 00170 CLR $71 00180 JMP [$FFFE] 00190 DONE EQU * 00200 END BEGIN [image: image] <https://user-images.githubusercontent.com/2383820/278796840-052e9701-c209-41e3-9299-88df35189530.png> [image: image] <https://user-images.githubusercontent.com/2383820/278796853-d7ca01ca-a928-4592-bfdd-bfdbf252dd0e.png> — Reply to this email directly, view it on GitHub <#150>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFIUKNFDVQR7TLK4ACUQV6DYBSVC7AVCNFSM6AAAAAA6T3BGPOVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE3DMNBXGE2DSMQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

On Sat, Oct 28, 2023, 11:35 PM Ting Tron ***@***.***> wrote: Yes, indeed when using the latest version VCC-2.1.8.1, that crashing issue with BIN command line parameter is resolved. (I thought I downloaded recently. But I could've selected a previous release by mistake.) But I am having another issue with the latest VCC-2.1.8.1: - When selecting menu: File / Exit, the application hangs, instead of existing. - When using the close [X] window frame icon, it exists normally. And this File / Exit issue doesn't seem to reported. If it's not already addressed elsewhere, I can create an issue for it. — Reply to this email directly, view it on GitHub <#150 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFIUKNEJNONYSJ4IOMZFYNLYBXFJTAVCNFSM6AAAAAA6T3BGPOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBTHE4DQOJVGQ> . You are receiving this because you commented.Message ID: ***@***.***>