Menu

#769 x64dtv using drive 1571 or 1570 error - emulation crash

v2.4.x
closed-wont-fix
nobody
None
Windows
x64dtv
2018-05-18
2016-07-23
MIRKOSOFT
No

I tried to use with x64dtv drive 1571. My config uses FD-4000 and tried to start with:
x64dtv -drive8type 1571
or later meaning it's problem of command line mismatch I tried to create separate configuration for use with -config, but always VICE reports error:
"An unexpected error occured. Received signal 8 ()."

I tested also other drives and else 1570 produces same error message and emulation crashes. All possible other drives working correctly, finally it was tested on default config.
Please fix it soon.

Miro

Discussion

  • MIRKOSOFT

    MIRKOSOFT - 2016-07-23

    I'm sorry - I forgot: Build 2.4.28 revision 31459

     
  • MIRKOSOFT

    MIRKOSOFT - 2016-08-17

    Here's LOG after x64dtv start.
    Miro

     
  • gpz

    gpz - 2016-08-17

    i can not reproduce this - please try again with a recent build and -default -drive8type 1571

     
  • MIRKOSOFT

    MIRKOSOFT - 2016-08-17

    Ok, tried - works only with default settings! If I try to add other DTV ROM or anything it crashes - also when I leave default 1571 ROM.
    Miro

     
  • gpz

    gpz - 2016-08-17

    please give a commandline that starts with -default that makes it crash

     
  • MIRKOSOFT

    MIRKOSOFT - 2016-12-01

    Again, please fix this bug before VICE 3.0 release.
    Attached is error message, log and config.
    Truth is that default config it produces not but default is 1541-II drive and default ROM.
    When this bug appeared, I tested it on older VICE 2.4.x revisions and worked perfectly.
    I'm 128er and really awaiting more FD-2000/4000 fix, but this too.

    Miro

     
  • Querino

    Querino - 2016-12-01

    i can confirm this bug

    • start c64dtv, default settings
    • set drive8 to 4000
    • save settings
    • close c64dtv
    • start c64dtv with "x64dtv -drive8type 1571"
    • ---> signal 8

    the same with -drive8type 1570, others seem to work

     
  • gpz

    gpz - 2016-12-01

    can't reproduce it like that in linux - might be a windows specific problem

     
  • compyx

    compyx - 2016-12-03

    Happens in Windows as far as can see. But no need to go through hoops. Just select 1570/1571 in the UI to cause the crash. That's in 2.4.32. In 2.4.33, the -drive8type command line and the Drive8Type setting in vice.ini cause crashes (when using 1570/1571). So it got worse in the latest build.

     
  • gpz

    gpz - 2018-05-18
    • status: open --> closed-wont-fix
     
  • gpz

    gpz - 2018-05-18

    Windows native UI will get removed after 3.2 - please test the GTK3 UI

     

Log in to post a comment.