-
This patch add weak data handling capability to Fuse.
Now we fdd.c can deal with weak data if it present in the disk image (EDSK/UDI).
Changes:
settings.dat:
- `plus3_detect_speedlock`: can switch on/off the UPD765 emulation Speedlock hack
- `drive_read_weak`: can switch on/off `fdd.c` weak data reading things
- `disk_save_compressed`: fuse try to create compressed UDI...
2010-01-07 15:50:49 UTC by szaszg
-
Thanks, committed in revision 4111.
2010-01-07 11:51:25 UTC by fredm
-
there are some problem around ui_widget_{init,end}(), so i upload a
little patch.
2010-01-06 14:59:01 UTC by szaszg
-
Here is an updated patch...
btw: there are some problem around ui_widget_{init,end}(), so i upload a little patch to #2918210.
2010-01-06 14:23:10 UTC by szaszg
-
OK, I'll commit the patch if you can clean it up a bit more (Fuse indentation and coding standards, remove C++ // comments in C comment blocks, remove commented out code etc.).
2010-01-05 10:44:41 UTC by fredm
-
Fuse cannot open and read compressed disk images and multiple compressed tapes etc.
In libspectrum `libspectrum_identify_file_with_class()` do recursive uncompression, so identify multiple compressed files (eg: chasehq.dsk.gz.gz, or Chaos.tzx.gz.gz).
In libspectrum `libspectrum_tape_read()` do only one level uncompression, so if we start fuse e.g.:
fuse Chaos.tzx.gz.gz
Fuse identify TZX...
2010-01-04 16:47:47 UTC by szaszg
-
About downsides:
1.) "presumably slightly worse performance" -- this is IMHO at least a questionable thing... but if we afraid of not inlined template arguments, we easily convert it to #defines, because FUSE use only one pair. The "less inlined code" is an another question, because we use -O2, so gcc decide about `inline` quite freely... btw. in the C source by default we avoid asset tests, so...
2009-12-31 13:19:14 UTC by szaszg
-
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
2009-12-31 02:20:18 UTC by sf-robot
-
I am in two minds about this. If the upstream author had a fully featured C version I would have used that originally*, but given the code is integrated and working as is, the reasons to change to C then are something like;
1) Fuse has traditionally been straight C
2) Having C++ means that you need a C++ compiler/runtime (is this a real issue in 2009 on any platform of interest?)
The...
2009-12-31 00:01:17 UTC by fredm
-
Thanks for the pointer, fixed in revision 4110.
2009-12-30 09:11:11 UTC by fredm
