Error writing Kryoflux stream

All questions about how to use KryoFlux go here.
User avatar
mr.vince
Posts: 2101
Joined: Tue Oct 05, 2010 5:48 pm

Re: Error writing Kryoflux stream

Post by mr.vince » Thu Mar 08, 2018 5:50 pm

Kingstener wrote:
Thu Mar 08, 2018 10:25 am
I thought the destination of the kryoflux and dtc is data rescue and recovery and not an uncooperative "We won't support such files" :-/
Absolutely. And exactly because of this we won't fix a program to accept invalid image files. The idea behind a standard is that it's there on purpose. In other words... if there's PDF converter that's producing PDFs which are non-standard and crash every PDF viewer, my vote is to fix the converter (making it produce compliant PDFs) instead of fixing every viewer out there and adding exemption over exemption to the standard. IFW has outlined what's wrong with the data, so future versions won't crash but identify the data as invalid.

Please note that this error does not happen with genuine dumps created by KryoFlux, hence it did go unnoticed.

User avatar
IFW
Posts: 3077
Joined: Mon Nov 08, 2010 2:42 pm

Re: Error writing Kryoflux stream

Post by IFW » Thu Mar 08, 2018 6:07 pm

I've fixed DTC so it won't crash anymore with these broken stream files.
The fix will be available from DTC version 2.72.
However do note that the stream files generated are faulty and may cause other issues in some cases.
There is no way to fix these files, other than fixing the program generating them as DTC cannot and should not guess what the correct data should be.
As I said there is another fault as well regarding cell sizes used by the generated files ultimately ending up bad, resulting in a sampling speed of 296 RPM instead of 300.
While this does not matter for DTC it undermines the readability of the generated data for a real FDC, using up it's tolerance that is there for cell tracking, not for compensating for non-standard bitcells...

Kingstener
Posts: 6
Joined: Sat Feb 17, 2018 9:11 am

Re: Error writing Kryoflux stream

Post by Kingstener » Fri Mar 09, 2018 10:38 am

@IFW
Thanks for your support, unfortunately Jeff is not so enthusiastic to help more with the possibility to convert over HxC.
So one can only try to make the most of it :-)

@ mr.vince
It is exhausting enough to fight through with dictionary and then to notice that there is nothing constructive in the text .
There were already some devices for data recovery of old disks, unfortunately, all bring their own format with them and at last they disappear sometime from the scene, then you sit on a data grave. So one depends on software that can convert these formats or the old computers are only for viewing or to scrap. And as I already noticed one is dependent on any hint that further help. I'm still a part of the generation that has experienced the beginning of computer history but also already have forgotten many things...
(And no, I will not convert a PDF and write to disk)

User avatar
mr.vince
Posts: 2101
Joined: Tue Oct 05, 2010 5:48 pm

Re: Error writing Kryoflux stream

Post by mr.vince » Fri Mar 09, 2018 12:09 pm

That's why our format is fully documented and open and everyone is free to convert into or use it as a source. And we're very constructive - a bug gets pointed out, and it got fixed and such fix will be released soon. There is a problem in the converter software you are using, so this must be fixed, not DTC, which is fine and broke because of bogus data fed into the processing pipeline.

The HxC software is open sourced, so that's good news again, as you don't depend on Jeff fixing it.

User avatar
IFW
Posts: 3077
Joined: Mon Nov 08, 2010 2:42 pm

Re: Error writing Kryoflux stream

Post by IFW » Fri Mar 09, 2018 2:34 pm

Indeed, the formats (all of them!) being documented is very important.

As mr. vince said we'll have a new DTC release soon (after testing etc); currently it's in its release candidate state.

Thanks a lot for posting about this problem :)

User avatar
DrCoolZic
Posts: 172
Joined: Tue Jul 26, 2011 10:44 am

Re: Error writing Kryoflux stream

Post by DrCoolZic » Thu Apr 26, 2018 10:50 pm

I just discovered yesterday that the files I generate are not read anymore by the new version of DTC.

@Kingstener
Will try to see if I can help Jeff to fix the problem after I understand mine :)
https://forum.kryoflux.com/viewtopic.ph ... 965#p13413

Kingstener
Posts: 6
Joined: Sat Feb 17, 2018 9:11 am

Re: Error writing Kryoflux stream

Post by Kingstener » Sun Apr 29, 2018 8:23 am

In the latest version of the HxC that should be fixed, at least I have no more error message.

Gunstick
Posts: 1
Joined: Fri Jan 01, 2016 9:50 am

Re: Error writing Kryoflux stream

Post by Gunstick » Mon Nov 12, 2018 11:38 pm

hi

I just compiled the newest version of HxC. And wanted to write an STX file to disk.
Well, hxcfe does not work. I help myself by first converting to ST and then to RAW (is usually fine if there is no fancy copy protection)

Code: Select all

Linux tardis 4.4.0-133-generic #159-Ubuntu SMP Fri Aug 10 07:31:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
LSB Version:	core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.5 LTS
Release:	16.04
Codename:	xenial



./hxcfe '-finput:/tmp/barbarian_2_(psygnosis)_(disk_1).stx' -foutput:/tmp/st2kf26502/image -conv:KRYOFLUXSTREAM
HxC Floppy Emulator : Floppy image file converter v2.0.2.1
Copyright (C) 2006-2018 Jean-Francois DEL NERO
This program comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions;

libhxcfe version : 2.9.1.1

Input file : /tmp/barbarian_2_(psygnosis)_(disk_1).stx
Output file : /tmp/st2kf26502/image
Checking /tmp/barbarian_2_(psygnosis)_(disk_1).stx
*** Error in `./hxcfe': free(): invalid pointer: 0x00007fff71485c08 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7f019fb5a7e5]
/lib/x86_64-linux-gnu/libc.so.6(+0x8037a)[0x7f019fb6337a]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7f019fb6753c]
./libhxcfe.so(STX_libIsValidDiskFile+0x8f)[0x7f01a018a80f]
./libhxcfe.so(hxcfe_imgAutoSetectLoader+0xc1)[0x7f01a015d621]
./hxcfe[0x402d4b]
./hxcfe[0x402303]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f019fb03830]
./hxcfe[0x4024e9]
======= Memory map: ========
00400000-00406000 r-xp 00000000 00:2e 2149367                            /home/georges/hxcfloppyemu-code-1354/hxcfloppyemu-code/HxCFloppyEmulator/build/hxcfe
00605000-00606000 r--p 00005000 00:2e 2149367                            /home/georges/hxcfloppyemu-code-1354/hxcfloppyemu-code/HxCFloppyEmulator/build/hxcfe
00606000-00607000 rw-p 00006000 00:2e 2149367                            /home/georges/hxcfloppyemu-code-1354/hxcfloppyemu-code/HxCFloppyEmulator/build/hxcfe
02212000-02611000 rw-p 00000000 00:00 0                                  [heap]
7f0198000000-7f0198021000 rw-p 00000000 00:00 0 
7f0198021000-7f019c000000 ---p 00000000 00:00 0 
7f019f1a3000-7f019f1b9000 r-xp 00000000 08:08 12058854                   /lib/x86_64-linux-gnu/libgcc_s.so.1
7f019f1b9000-7f019f3b8000 ---p 00016000 08:08 12058854                   /lib/x86_64-linux-gnu/libgcc_s.so.1
7f019f3b8000-7f019f3b9000 rw-p 00015000 08:08 12058854                   /lib/x86_64-linux-gnu/libgcc_s.so.1
7f019f3b9000-7f019f3bc000 r-xp 00000000 08:08 12085833                   /lib/x86_64-linux-gnu/libdl-2.23.so
7f019f3bc000-7f019f5bb000 ---p 00003000 08:08 12085833                   /lib/x86_64-linux-gnu/libdl-2.23.so
7f019f5bb000-7f019f5bc000 r--p 00002000 08:08 12085833                   /lib/x86_64-linux-gnu/libdl-2.23.so
7f019f5bc000-7f019f5bd000 rw-p 00003000 08:08 12085833                   /lib/x86_64-linux-gnu/libdl-2.23.so
7f019f5bd000-7f019f6c5000 r-xp 00000000 08:08 12058695                   /lib/x86_64-linux-gnu/libm-2.23.so
7f019f6c5000-7f019f8c4000 ---p 00108000 08:08 12058695                   /lib/x86_64-linux-gnu/libm-2.23.so
7f019f8c4000-7f019f8c5000 r--p 00107000 08:08 12058695                   /lib/x86_64-linux-gnu/libm-2.23.so
7f019f8c5000-7f019f8c6000 rw-p 00108000 08:08 12058695                   /lib/x86_64-linux-gnu/libm-2.23.so
7f019f8c6000-7f019f8de000 r-xp 00000000 08:08 12085810                   /lib/x86_64-linux-gnu/libpthread-2.23.so
7f019f8de000-7f019fadd000 ---p 00018000 08:08 12085810                   /lib/x86_64-linux-gnu/libpthread-2.23.so
7f019fadd000-7f019fade000 r--p 00017000 08:08 12085810                   /lib/x86_64-linux-gnu/libpthread-2.23.so
7f019fade000-7f019fadf000 rw-p 00018000 08:08 12085810                   /lib/x86_64-linux-gnu/libpthread-2.23.so
7f019fadf000-7f019fae3000 rw-p 00000000 00:00 0 
7f019fae3000-7f019fca3000 r-xp 00000000 08:08 12085830                   /lib/x86_64-linux-gnu/libc-2.23.so
7f019fca3000-7f019fea3000 ---p 001c0000 08:08 12085830                   /lib/x86_64-linux-gnu/libc-2.23.so
7f019fea3000-7f019fea7000 r--p 001c0000 08:08 12085830                   /lib/x86_64-linux-gnu/libc-2.23.so
7f019fea7000-7f019fea9000 rw-p 001c4000 08:08 12085830                   /lib/x86_64-linux-gnu/libc-2.23.so
7f019fea9000-7f019fead000 rw-p 00000000 00:00 0 
7f019fead000-7f019feb3000 r-xp 00000000 00:2e 2149362                    /home/georges/hxcfloppyemu-code-1354/hxcfloppyemu-code/HxCFloppyEmulator/build/libusbhxcfe.so
7f019feb3000-7f01a00b3000 ---p 00006000 00:2e 2149362                    /home/georges/hxcfloppyemu-code-1354/hxcfloppyemu-code/HxCFloppyEmulator/build/libusbhxcfe.so
7f01a00b3000-7f01a00b4000 r--p 00006000 00:2e 2149362                    /home/georges/hxcfloppyemu-code-1354/hxcfloppyemu-code/HxCFloppyEmulator/build/libusbhxcfe.so
7f01a00b4000-7f01a00b5000 rw-p 00007000 00:2e 2149362                    /home/georges/hxcfloppyemu-code-1354/hxcfloppyemu-code/HxCFloppyEmulator/build/libusbhxcfe.so
7f01a00b5000-7f01a0139000 rw-p 00000000 00:00 0 
7f01a0139000-7f01a0241000 r-xp 00000000 00:2e 2149357                    /home/georges/hxcfloppyemu-code-1354/hxcfloppyemu-code/HxCFloppyEmulator/build/libhxcfe.so
7f01a0241000-7f01a0440000 ---p 00108000 00:2e 2149357                    /home/georges/hxcfloppyemu-code-1354/hxcfloppyemu-code/HxCFloppyEmulator/build/libhxcfe.so
7f01a0440000-7f01a0443000 r--p 00107000 00:2e 2149357                    /home/georges/hxcfloppyemu-code-1354/hxcfloppyemu-code/HxCFloppyEmulator/build/libhxcfe.so
7f01a0443000-7f01a04a3000 rw-p 0010a000 00:2e 2149357                    /home/georges/hxcfloppyemu-code-1354/hxcfloppyemu-code/HxCFloppyEmulator/build/libhxcfe.so
7f01a04a3000-7f01a1a0d000 rw-p 00000000 00:00 0 
7f01a1a0d000-7f01a1a33000 r-xp 00000000 08:08 12085804                   /lib/x86_64-linux-gnu/ld-2.23.so
7f01a1a92000-7f01a1c04000 rw-p 00000000 00:00 0 
7f01a1c30000-7f01a1c32000 rw-p 00000000 00:00 0 
7f01a1c32000-7f01a1c33000 r--p 00025000 08:08 12085804                   /lib/x86_64-linux-gnu/ld-2.23.so
7f01a1c33000-7f01a1c34000 rw-p 00026000 08:08 12085804                   /lib/x86_64-linux-gnu/ld-2.23.so
7f01a1c34000-7f01a1c35000 rw-p 00000000 00:00 0 
7fff71467000-7fff71488000 rw-p 00000000 00:00 0                          [stack]
7fff71593000-7fff71596000 r--p 00000000 00:00 0                          [vvar]
7fff71596000-7fff71598000 r-xp 00000000 00:00 0                          [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]
./st2kryoflux-floppy.sh: line 19: 26509 Aborted                 (core dumped) ./hxcfe -finput:"$source" -foutput:"$dest" -conv:KRYOFLUXSTREAM
EDIT mr.vince: look how pretty this can be...

Jeff_HxC2001
Posts: 58
Joined: Thu May 12, 2011 10:56 pm

Re: Error writing Kryoflux stream

Post by Jeff_HxC2001 » Sun Nov 18, 2018 7:28 am

Gunstick wrote:
Mon Nov 12, 2018 11:38 pm
hi

I just compiled the newest version of HxC. And wanted to write an STX file to disk.
Well, hxcfe does not work. I help myself by first converting to ST and then to RAW (is usually fine if there is no fancy copy protection)
This can happen when you use a dev/work-in-progress version. :D

Anyway this issue is now fixed on the trunk repository :
https://sourceforge.net/p/hxcfloppyemu/code/HEAD/tree/

(and btw old tagged version are unaffected by this issue)

User avatar
mr.vince
Posts: 2101
Joined: Tue Oct 05, 2010 5:48 pm

Re: Error writing Kryoflux stream

Post by mr.vince » Mon Nov 19, 2018 3:34 pm

Please use proper formatting for logs (code tags) to avoid cluttering the whole screen. Thanks.

Post Reply