fuse-emulator-devel — Development of Fuse (the Free Unix Spectrum Emulator), the associated utilities and libspectrum, the ZX Spectrum file-format handling library.

[fuse-emulator-devel] Speed "surge"

[Phil R. <phi...@ti...>]

Recently I have noticed the emulation speed surging to 2500% or so then
slowly dropping back - an effect I'd not seen before. It seems to
happen after using the menus, among other things.

This is on Debian bullseye, using a self compiled fuse and libspectrum.
What could be causing this odd effect?

-- 
Phil Reynolds
mail: phi...@ti...
Web: http://phil.tinsleyviaduct.com/

[fuse-emulator-devel] Spectranet snapshot blocks

[Alistair <ali...@zx...>]

I've been trying to make sense of the .szx files Fuse creates with 
spectranet enabled, which didn't match the description Phil had added to 
the sinclair wiki

https://sinclair.wiki.zxnet.co.uk/wiki/ZX-State_format#ZXSTSPECTRANETFLASHPAGE

I've made an edit to change wFlags to chFlags and add two DWORDs but I 
can't fathom what the first is supposed to be. When the snapshot is 
converted to uncompressed with snapconv it comes out holding a 
big-endian copy of the data size, but on compressed snapshots I can't 
make head or tails of it.

It's apparently the value of flash_buffer->bytes_used when the snef 
chunk is being written, but I've seen values from 1 to petabytes.

Re: [fuse-emulator-devel] Doubled printout (at least in +3 mode)

[Phil R. <phi...@ti...>]

On Sun, 13 Nov 2022 18:52:25 +0000
Phil Reynolds <phi...@ti...> wrote:

> Oddly enough, Tasword Plus Two seems to work fine (on a +2 emulation).
> This is just one of those things I wanted to experiment with.
> Unfortunately my preferred version of TLW is not available on WOS yet
> - it's not dissimilar to the +3 version but was a cassette with disk
> system conversion instructions in the manual. (version 2.2 possibly?)
 
Definite TLW bug - Tasword Plus Three performs correctly on printing.
Still on the lookout for the version of TLW I had - it's just a step
towards completing the gathering of what I would have obtained myself.
That's not to say I mightn't have considered Tasword suited to whatever
kind of 128 I'd had, but without the manual I can't be sure I would
have gone for it.

-- 
Phil Reynolds
mail: phi...@ti...
Web: http://phil.tinsleyviaduct.com/

Re: [fuse-emulator-devel] Doubled printout (at least in +3 mode)

[Phil R. <phi...@ti...>]

On Thu, 20 Oct 2022 18:29:04 +0000
Szász Gergely <sz...@hu...> wrote:

> On Sun, Oct 16, 2022 at 04:05:02PM +0100, Phil Reynolds wrote:
> > Trying to investigate methods of printer emulation, I have tried to
> > print from the +3 version of "The Last Word" - but printout.txt
> > seems to contain doubled up characters compared to what is actually
> > in the file - so "SSppeeccttrruumm" where the file contains
> > "Spectrum", for example.
> > 
> > Have I got something mis-set that would be causing this or is it a
> > bug? This is in 1.6.0.
> > 
> > -- 
> > Phil Reynolds
> > mail: phi...@ti...
> > Web: http://phil.tinsleyviaduct.com/  
> 
> Hello Phil,
> 
> The print routine try to recognise the bitmaps (OCR) and save this
> recognised text.
> 
> In the code there is a routine for graphics output (pbm), but i don't
> know (at now) how to activate...
> 
> 
> I test with a git version before 2021.11 (1.6.0) and the LLIST works
> as excepted (128K and +3 too).
> 
> Can you try LPRINT or LLIST?

Hmmm... no problem there... must be a TLW issue. Intend to try some
other similar apps on other emulations too... it ought to work a bit
better than suggested.

-- 
Phil Reynolds
mail: phi...@ti...
Web: http://phil.tinsleyviaduct.com/

Re: [fuse-emulator-devel] Doubled printout (at least in +3 mode)

[Phil R. <phi...@ti...>]

On Thu, 20 Oct 2022 18:29:04 +0000
Szász Gergely <sz...@hu...> wrote:

> On Sun, Oct 16, 2022 at 04:05:02PM +0100, Phil Reynolds wrote:
> > Trying to investigate methods of printer emulation, I have tried to
> > print from the +3 version of "The Last Word" - but printout.txt
> > seems to contain doubled up characters compared to what is actually
> > in the file - so "SSppeeccttrruumm" where the file contains
> > "Spectrum", for example.
> > 
> > Have I got something mis-set that would be causing this or is it a
> > bug? This is in 1.6.0.
> > 
> > -- 
> > Phil Reynolds
> > mail: phi...@ti...
> > Web: http://phil.tinsleyviaduct.com/  
> 
> Hello Phil,
> 
> The print routine try to recognise the bitmaps (OCR) and save this
> recognised text.
> 
> In the code there is a routine for graphics output (pbm), but i don't
> know (at now) how to activate...
> 
> 
> I test with a git version before 2021.11 (1.6.0) and the LLIST works
> as excepted (128K and +3 too).
> 
> Can you try LPRINT or LLIST?

Oddly enough, Tasword Plus Two seems to work fine (on a +2 emulation).
This is just one of those things I wanted to experiment with.
Unfortunately my preferred version of TLW is not available on WOS yet -
it's not dissimilar to the +3 version but was a cassette with disk
system conversion instructions in the manual. (version 2.2 possibly?)

-- 
Phil Reynolds
mail: phi...@ti...
Web: http://phil.tinsleyviaduct.com/

[fuse-emulator-devel] Spectranet emulation patch

[Alistair <ali...@zx...>]

I'm not sure if anyone gets alerts for sourceforge merge requests, so 
bumping here.

https://sourceforge.net/p/fuse-emulator/fuse/merge-requests/10/

Guesser

Re: [fuse-emulator-devel] Doubled printout (at least in +3 mode)

[Szász G. <sz...@hu...>]

On Sun, Oct 16, 2022 at 04:05:02PM +0100, Phil Reynolds wrote:
> Trying to investigate methods of printer emulation, I have tried to
> print from the +3 version of "The Last Word" - but printout.txt seems
> to contain doubled up characters compared to what is actually in the
> file - so "SSppeeccttrruumm" where the file contains "Spectrum", for
> example.
> 
> Have I got something mis-set that would be causing this or is it a bug?
> This is in 1.6.0.
> 
> -- 
> Phil Reynolds
> mail: phi...@ti...
> Web: http://phil.tinsleyviaduct.com/

Hello Phil,

The print routine try to recognise the bitmaps (OCR) and save this recognised text.

In the code there is a routine for graphics output (pbm), but i don't know (at now) how to activate...


I test with a git version before 2021.11 (1.6.0) and the LLIST works as excepted (128K and +3 too).

Can you try LPRINT or LLIST?

Gergely

[fuse-emulator-devel] Doubled printout (at least in +3 mode)

[Phil R. <phi...@ti...>]

Trying to investigate methods of printer emulation, I have tried to
print from the +3 version of "The Last Word" - but printout.txt seems
to contain doubled up characters compared to what is actually in the
file - so "SSppeeccttrruumm" where the file contains "Spectrum", for
example.

Have I got something mis-set that would be causing this or is it a bug?
This is in 1.6.0.

-- 
Phil Reynolds
mail: phi...@ti...
Web: http://phil.tinsleyviaduct.com/

[fuse-emulator-devel] Help

[super h. <ffx...@gm...>]

I keep getting the rom log blue screen 

[fuse-emulator-devel] bug in ZX Printer emulation?

[Cygnus <cy...@po...>]

Hello, I am working on new version of old text editor. Small part of 
this editor is subroutine for printing on ZX Printer. And i found it 
doesn't print last pixels. One last pixel on every pixel line is missing.

Of course i suspected code from text editor first, but it only copies 
one text line from screen to the ZX Printer buffer on address 23296 and 
then it is calling subroutine in ZX ROM at 3789 (0xecd).

And BASIC command COPY behaves very similarly, last pixels are mostly 
missing. So it is definitely error in ROM or in ZX Printer emulation.

Interestingly with command COPY are not missing all last pixels, i have 
no idea why, but result is still not correct.

See screenshots - all black pixels are correct, missing pixels are red, 
which i added in Gimp to be clear what is wrong.


Cygnus

Re: [fuse-emulator-devel] cannot format single side TRDOS disk

[Szász G. <sz...@hu...>]

On Fri, Nov 19, 2021 at 04:05:52PM +0100, Cygnus wrote:
> Didn't help either.
> 
> What finally help - i just copied all libspectrum files in /usr/lib64
> instead /usr/local/lib even include/libspectrum.h in /usr/include and
> pkconfig/libspectrum.pc in /usr/lib64/pkconfig ...
> 
> It is bad practice, but it worked. Now i can test *Fuse 1.6.0*
> 
> So back to the TRDOS. It's behaviour with other disk formats than 640kB is
> still the same.
> 
> *How to replicate:*
> 
> 1/ select any ZX Spectrum and Betadisk emulation
> 
> Usually i am using ZX Spectrum 128k +2 with ISO ROM and TRDOS 5.05cz, but i
> tested it with Pentagon 128 and default TRDOS 5.03. It behaves exactly same
> (but TRDOS is much more slower).
> 
> 2/ in emulator "Media" -> "Beta" -> "Drive A" -> "Insert new"
> 
> 3/ in TRDOS command FORMAT "$" - will format disk as 80 track single sided
> with capacity 1264 sectors
> 
> (another possibility is command 40 before FORMAT or 40 and $ in disk name =
> 160kB disk)
> 
> 4/ just for fun in TRDOS command line save one file, for example SAVE "aaa"
> CODE 0,16384 and then CAT or LIST - everything is still fine
> 
> 5/ in emulator "Media" -> "Beta" -> "Drive A" -> "Save As"
> 
> 6/ now it fails with this error message and TRD image is empty (file size is
> zero instead 320kB or 640kB with unused second half)
> 
> 
> 
> 
> 
> Cygnus

Hi,

If you just want to test:
first compile libspectrum:
cd libspectrum
./configure --prefix=`pwd`
make
make install

than compile fuse:

cd ../fuse
export PKG_CONFIG_PATH=../libspectrum/lib/pkgconfig
./configure
make

now you can run fuse from here:
./fuse

----

You can save any disk "image" as a "log" file to see what is on the disk, just save as any_name.log

The problem is that: you insert a double sided 80 track disk, TR-DOS format only side 0 (*) and fuse cannot save unformatted tracks into TRD image (side 1).

You have to select "Single-sided 80 track" drive (Options->Disk Options->Beta 128 Drive [ABCD]) before insert a "new" disk, because fuse when insert a new disk use the same disk geometry as the drive has.

* Very strange: TR-DOS format Side 0 track 0-79 and Side 1 track 0 (but no other tracks on side 1) with FORMAT "$"... hmm?

Cheers,
Gergely

==========================
DISK tracks log!
Sides: 2, cylinders: 80

*********
Side: 0, cylinder: 0 type: 0x00 tlen:  6250
  h:0 t:0 s:1 l:1(256) normal
  h:0 t:0 s:9 l:1(256) normal
  h:0 t:0 s:2 l:1(256) normal
  h:0 t:0 s:10 l:1(256) normal
  h:0 t:0 s:3 l:1(256) normal
  h:0 t:0 s:11 l:1(256) normal
  h:0 t:0 s:4 l:1(256) normal
  h:0 t:0 s:12 l:1(256) normal
  h:0 t:0 s:5 l:1(256) normal
  h:0 t:0 s:13 l:1(256) normal
  h:0 t:0 s:6 l:1(256) normal
  h:0 t:0 s:14 l:1(256) normal
  h:0 t:0 s:7 l:1(256) normal
  h:0 t:0 s:15 l:1(256) normal
  h:0 t:0 s:8 l:1(256) normal
  h:0 t:0 s:16 l:1(256) normal

*********
Side: 1, cylinder: 0 type: 0x00 tlen:  6250
  h:0 t:1 s:1 l:1(256) normal
  h:0 t:1 s:9 l:1(256) normal
  h:0 t:1 s:2 l:1(256) normal
  h:0 t:1 s:10 l:1(256) normal
  h:0 t:1 s:3 l:1(256) normal
  h:0 t:1 s:11 l:1(256) normal
  h:0 t:1 s:4 l:1(256) normal
  h:0 t:1 s:12 l:1(256) normal
  h:0 t:1 s:5 l:1(256) normal
  h:0 t:1 s:13 l:1(256) normal
  h:0 t:1 s:6 l:1(256) normal
  h:0 t:1 s:14 l:1(256) normal
  h:0 t:1 s:7 l:1(256) normal
  h:0 t:1 s:15 l:1(256) normal
  h:0 t:1 s:8 l:1(256) normal
  h:0 t:1 s:16 l:1(256) normal

*********
Side: 0, cylinder: 1 type: 0x00 tlen:  6250
  h:0 t:1 s:1 l:1(256) normal
  h:0 t:1 s:9 l:1(256) normal
  h:0 t:1 s:2 l:1(256) normal
  h:0 t:1 s:10 l:1(256) normal
  h:0 t:1 s:3 l:1(256) normal
  h:0 t:1 s:11 l:1(256) normal
  h:0 t:1 s:4 l:1(256) normal
  h:0 t:1 s:12 l:1(256) normal
  h:0 t:1 s:5 l:1(256) normal
  h:0 t:1 s:13 l:1(256) normal
  h:0 t:1 s:6 l:1(256) normal
  h:0 t:1 s:14 l:1(256) normal
  h:0 t:1 s:7 l:1(256) normal
  h:0 t:1 s:15 l:1(256) normal
  h:0 t:1 s:8 l:1(256) normal
  h:0 t:1 s:16 l:1(256) normal

*********
Side: 1, cylinder: 1 type: 0x00 tlen:  6250

*********
Side: 0, cylinder: 2 type: 0x00 tlen:  6250
  h:0 t:2 s:1 l:1(256) normal
  h:0 t:2 s:9 l:1(256) normal
  h:0 t:2 s:2 l:1(256) normal
  h:0 t:2 s:10 l:1(256) normal
  h:0 t:2 s:3 l:1(256) normal
  h:0 t:2 s:11 l:1(256) normal
  h:0 t:2 s:4 l:1(256) normal
  h:0 t:2 s:12 l:1(256) normal
=====================

Gergely
> 
> 
> 
> Dne 19. 11. 21 v 14:25 Tomáš Franke napsal(a):
> > |It was the same when I compiled it on Raspberry Pi from sources Try
> > this Build the library, with the default path, install it, sudo rm
> > /etc/ld.so.cache sudo ldconfig then ./configure all the packages that
> > uses the library again Omikron |
> > Dne 19. 11. 21 v 13:51 Cygnus napsal(a):
> > > I tried latest release in combination:
> > > 
> > > fuse-utils-1.4.3
> > > fuse-1.6.0
> > > libspectrum-1.5.0
> > > 
> > > But it was total fail. I compiled and installed libspectrum first as
> > > usual and then i tried configure fuse emulator, but configure script
> > > was never able found libspectrum, i ended with
> > > 
> > > checking for LIBSPECTRUM... no
> > > configure: error: Package requirements (libspectrum >= 1.5.0) were
> > > not met:
> > > 
> > > No package 'libspectrum' found
> > > 
> > > Consider adjusting the PKG_CONFIG_PATH environment variable if you
> > > installed software in a non-standard prefix.
> > > 
> > > Parameter --prefix=/opt/fuse instead default path /usr/local did not
> > > help. (Of course i used same path for all packages, especially
> > > libspectrum and emulator).
> > > 
> > > So for now i am back to version 1.5.7.
> > > 
> > > Maybe later i will try it again on another computer with different
> > > Linux. I am sorry, but i am not able diagnose it better.
> > > 
> > > 
> > > Cygnus
> > > 
> > > 


> _______________________________________________
> fuse-emulator-devel mailing list
> fus...@li...
> https://lists.sourceforge.net/lists/listinfo/fuse-emulator-devel

Re: [fuse-emulator-devel] cannot format single side TRDOS disk

[Cygnus <cy...@po...>]

Didn't help either.

What finally help - i just copied all libspectrum files in /usr/lib64 
instead /usr/local/lib even include/libspectrum.h in /usr/include and 
pkconfig/libspectrum.pc in /usr/lib64/pkconfig ...

It is bad practice, but it worked. Now i can test *Fuse 1.6.0*

So back to the TRDOS. It's behaviour with other disk formats than 640kB 
is still the same.

*How to replicate:*

1/ select any ZX Spectrum and Betadisk emulation

Usually i am using ZX Spectrum 128k +2 with ISO ROM and TRDOS 5.05cz, 
but i tested it with Pentagon 128 and default TRDOS 5.03. It behaves 
exactly same (but TRDOS is much more slower).

2/ in emulator "Media" -> "Beta" -> "Drive A" -> "Insert new"

3/ in TRDOS command FORMAT "$" - will format disk as 80 track single 
sided with capacity 1264 sectors

(another possibility is command 40 before FORMAT or 40 and $ in disk 
name = 160kB disk)

4/ just for fun in TRDOS command line save one file, for example SAVE 
"aaa" CODE 0,16384 and then CAT or LIST - everything is still fine

5/ in emulator "Media" -> "Beta" -> "Drive A" -> "Save As"

6/ now it fails with this error message and TRD image is empty (file 
size is zero instead 320kB or 640kB with unused second half)





Cygnus



Dne 19. 11. 21 v 14:25 Tomáš Franke napsal(a):
> |It was the same when I compiled it on Raspberry Pi from sources Try 
> this Build the library, with the default path, install it, sudo rm 
> /etc/ld.so.cache sudo ldconfig then ./configure all the packages that 
> uses the library again Omikron |
> Dne 19. 11. 21 v 13:51 Cygnus napsal(a):
>> I tried latest release in combination:
>>
>> fuse-utils-1.4.3
>> fuse-1.6.0
>> libspectrum-1.5.0
>>
>> But it was total fail. I compiled and installed libspectrum first as 
>> usual and then i tried configure fuse emulator, but configure script 
>> was never able found libspectrum, i ended with
>>
>> checking for LIBSPECTRUM... no
>> configure: error: Package requirements (libspectrum >= 1.5.0) were 
>> not met:
>>
>> No package 'libspectrum' found
>>
>> Consider adjusting the PKG_CONFIG_PATH environment variable if you
>> installed software in a non-standard prefix.
>>
>> Parameter --prefix=/opt/fuse instead default path /usr/local did not 
>> help. (Of course i used same path for all packages, especially 
>> libspectrum and emulator).
>>
>> So for now i am back to version 1.5.7.
>>
>> Maybe later i will try it again on another computer with different 
>> Linux. I am sorry, but i am not able diagnose it better.
>>
>>
>> Cygnus
>>
>>

Re: [fuse-emulator-devel] cannot format single side TRDOS disk

[Cygnus <cy...@po...>]

I tried latest release in combination:

fuse-utils-1.4.3
fuse-1.6.0
libspectrum-1.5.0

But it was total fail. I compiled and installed libspectrum first as 
usual and then i tried configure fuse emulator, but configure script was 
never able found libspectrum, i ended with

checking for LIBSPECTRUM... no
configure: error: Package requirements (libspectrum >= 1.5.0) were not met:

No package 'libspectrum' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Parameter --prefix=/opt/fuse instead default path /usr/local did not 
help. (Of course i used same path for all packages, especially 
libspectrum and emulator).

So for now i am back to version 1.5.7.

Maybe later i will try it again on another computer with different 
Linux. I am sorry, but i am not able diagnose it better.


Cygnus


Dne 19. 11. 21 v 6:36 Szász Gergely napsal(a):
> Hello,
>
> If i remember well, all format "emulated"... please try a "fresh" release. If no changes please write some more detail (a bug on SF?) and i try to find the problem. BTW there are a lot of patch around the floppy disk/drive "subsystem" in the tracking system waiting to commit :(
>
> What about "normal disk drives"? :) And "normal disks"? At that time there are "a lot of" single sided disk drives. Yes after the '90 (i think mainly the russian clones) uses "normal" PC-AT 3.5" floppy drives (2 headed) with "double sided" disks. But "douple sided" disks (or even "flippies") can be used in "single headed" drives too (as Alan wrote).
>
> Theoretically Betadisk can uses single head, double density drives.
>
> BTW the "flip disk" feature is a "general" for all disk interface in fuse.
>
> Cheer,
> Gergely
> On Tue, Nov 16, 2021 at 08:47:33PM +0100, Cygnus wrote:
>> Not sure if it wasn't already repaired (i am using older Fuse emulator
>> 1.5.7), but when i tried format new virtual TRDOS disk single sided i cannot
>> save it in TRD image. Only 640kB disks works.
>>
>>
>>
>> Why? Shouldn't be emulated all four possible formats?
>>
>> 40 tracks, single sided = 160kB (624 sectors)
>> 40 tracks, double sided = 320kB (1264 sectors)
>> 80 tracks, single sided = 320kB (1264 sectors)
>> 80 tracks, double sided = 640kB (2544 sectors)
>>
>> Why is in emulator option "Flip disk"? It doesn't make sense for me. Real
>> Betadisk is using normal disk drives and normal disks with only one index
>> hole and one write protect notch, it is not like on Commodore C64 or Atari
>> etc...
>>
>> Cygnus
>
>> _______________________________________________
>> fuse-emulator-devel mailing list
>> fus...@li...
>> https://lists.sourceforge.net/lists/listinfo/fuse-emulator-devel
>
>
> _______________________________________________
> fuse-emulator-devel mailing list
> fus...@li...
> https://lists.sourceforge.net/lists/listinfo/fuse-emulator-devel

Re: [fuse-emulator-devel] cannot format single side TRDOS disk

[Szász G. <sz...@hu...>]

Hello,

If i remember well, all format "emulated"... please try a "fresh" release. If no changes please write some more detail (a bug on SF?) and i try to find the problem. BTW there are a lot of patch around the floppy disk/drive "subsystem" in the tracking system waiting to commit :(

What about "normal disk drives"? :) And "normal disks"? At that time there are "a lot of" single sided disk drives. Yes after the '90 (i think mainly the russian clones) uses "normal" PC-AT 3.5" floppy drives (2 headed) with "double sided" disks. But "douple sided" disks (or even "flippies") can be used in "single headed" drives too (as Alan wrote).

Theoretically Betadisk can uses single head, double density drives.

BTW the "flip disk" feature is a "general" for all disk interface in fuse.

Cheer,
Gergely
On Tue, Nov 16, 2021 at 08:47:33PM +0100, Cygnus wrote:
> Not sure if it wasn't already repaired (i am using older Fuse emulator
> 1.5.7), but when i tried format new virtual TRDOS disk single sided i cannot
> save it in TRD image. Only 640kB disks works.
> 
> 
> 
> Why? Shouldn't be emulated all four possible formats?
> 
> 40 tracks, single sided = 160kB (624 sectors)
> 40 tracks, double sided = 320kB (1264 sectors)
> 80 tracks, single sided = 320kB (1264 sectors)
> 80 tracks, double sided = 640kB (2544 sectors)
> 
> Why is in emulator option "Flip disk"? It doesn't make sense for me. Real
> Betadisk is using normal disk drives and normal disks with only one index
> hole and one write protect notch, it is not like on Commodore C64 or Atari
> etc...
> 
> Cygnus


> _______________________________________________
> fuse-emulator-devel mailing list
> fus...@li...
> https://lists.sourceforge.net/lists/listinfo/fuse-emulator-devel

Re: [fuse-emulator-devel] cannot format single side TRDOS disk

[Cygnus <cy...@po...>]

Dne 17. 11. 21 v 12:33 Alan Cox napsal(a):
>> Why is in emulator option "Flip disk"? It doesn't make sense for me.
>> Real Betadisk is using normal disk drives and normal disks with only one
>> index hole and one write protect notch, it is not like on Commodore C64
>> or Atari etc...
> Some of the other disk types are flippable. In particular 3" disks were
> flippable so if you have a 3" drive attached to your system it makes
> total sense.
>
> (In some cases it's also possible to punch a second write protect hole in
> a 5.25" disk and that was sufficient on many systems)
>
> Alan
>
Yes, you are right, it is theoretically possible, but i never saw 
Betadisk with other than 3.5" or 5.25" drive. In one old article from 
1989 was mentioned 8" drive as possibility, but in real life no one used 
it (i remember it needed different crystal in clock oscillator for 
WD1793). 3" drives with Betadisk are probably even more rare.

I am using Betadisk maybe 30 years and during that time, most users from 
i heard about, had standard 3.5" or 5.25" drive double sided with 80 
tracks. In my experience it is definitely the most used configuration. 
So i understand it is the one which is emulated and preferred.

But i was just surprised when i discovered, so smaller 160kB or 320kB 
disk image cannot be saved, only 640kB can be. That's all.

I don't expect many users which will ever need it. I just tried it only 
during debugging one of my programs for which i need all disk format 
variants. No problem debug it on real hardware.


Btw... i really appreciated the possibility get data transmitted through 
ZXS 128k serial port into file (printout.txt). It was unexpected, but 
already several times very useful.



Thanks
Cygnus

Re: [fuse-emulator-devel] cannot format single side TRDOS disk

[Alan C. <al...@ll...>]

> Why is in emulator option "Flip disk"? It doesn't make sense for me. 
> Real Betadisk is using normal disk drives and normal disks with only one 
> index hole and one write protect notch, it is not like on Commodore C64 
> or Atari etc...

Some of the other disk types are flippable. In particular 3" disks were
flippable so if you have a 3" drive attached to your system it makes
total sense.

(In some cases it's also possible to punch a second write protect hole in
a 5.25" disk and that was sufficient on many systems)

Alan

[fuse-emulator-devel] cannot format single side TRDOS disk

[Cygnus <cy...@po...>]

Not sure if it wasn't already repaired (i am using older Fuse emulator 
1.5.7), but when i tried format new virtual TRDOS disk single sided i 
cannot save it in TRD image. Only 640kB disks works.



Why? Shouldn't be emulated all four possible formats?

40 tracks, single sided = 160kB (624 sectors)
40 tracks, double sided = 320kB (1264 sectors)
80 tracks, single sided = 320kB (1264 sectors)
80 tracks, double sided = 640kB (2544 sectors)

Why is in emulator option "Flip disk"? It doesn't make sense for me. 
Real Betadisk is using normal disk drives and normal disks with only one 
index hole and one write protect notch, it is not like on Commodore C64 
or Atari etc...

Cygnus

Re: [fuse-emulator-devel] game : Three Weeks in Paradise

[Alberto G. <be...@ig...>]

Snapshots don't store information about those options.

You could store them permanently using Options -> Save from the menu,
but if you do that you should also disable joystick emulation in
Options -> Josticks -> Keyboard when you are not playing a game.

About the extensions, use .szx.

Berto

On Tue, Oct 26, 2021 at 08:28:46PM +0200, Adam Sulmicki wrote:
> Hello Alberto.
> 
> Thank  you very much for your help.
> 
> I followed your directions and it did help me.
> 
> However it seems that the command line options are not preserved when
> saving and then restoring snapshot. After the restore the keys does
> not work anymore.
> 
> PS: What extension should have the snapshot files ?
> 
> Sincerely,
> Adam Sulmicki
> 
> On 10/26/21, Alberto Garcia <be...@ig...> wrote:
> > On Tue, Oct 26, 2021 at 05:50:21AM +0200, Adam Sulmicki wrote:
> >> I am trying to play : Three Weeks in Paradise
> >>
> >> https://www.worldofspectrum.org//pub/sinclair/games/t/ThreeWeeksInParadise128(different).tzx.zip
> >>
> >> I can't seem to get arrow keys working in the game. Any help?
> >
> > Hi!
> >
> > This list is for discussions about the development of the emulator,
> > not about general usage. You can use the Help forums for that:
> > https://sourceforge.net/p/fuse-emulator/discussion/
> >
> > But I think we actually have a bug, so I'll take the opportunity to
> > share the details :-)
> >
> > First, the answer for your question:
> >
> > Three Weeks in Paradise does not support the cursor keys or cursor
> > joystick, but you can emulate a joystick using your computer's arrow
> > keys:
> >
> > $ fuse --kempston --joystick-keyboard-output 2 --joystick-keyboard-up 256
> > --joystick-keyboard-down 257 --joystick-keyboard-left 258
> > --joystick-keyboard-right 259 --joystick-keyboard-fire 32 -m 128
> > ThreeWeeksInParadise.tzx
> >
> > Once the game is loaded, select "2. KEMPSTON" from the game menu. The
> > controls are the arrow keys and space to jump.
> >
> > Now, for the rest of the team:
> >
> > The "Configure joystick" dialog allows mapping Spectrum keys (enum
> > keyboard_key_name) to the joystick controls but then the native keys
> > (enum input_key) are the ones actually used.
> >
> > Two ways to see that:
> >
> > 1) Emulate a cursor joystick and use code 274 (INPUT_KEY_F8) for the
> >    fire button:
> >
> >    $ fuse --joystick-keyboard-output 1 --joystick-keyboard-fire 274
> >
> >    Press F8 and you'll see joystick fire ("0") on the screen, although
> >    F8 is not a Spectrum key.
> >
> > 2) Open Options -> Joysticks -> Keyboard, select "Cursor" type and
> >    Button for FIRE -> Enter.
> >
> >    Now if you press ENTER you should see joystick fire ("0"). Instead
> >    you'll only see that if you press Arrow Up.
> >
> >    And this is because INPUT_KEY_Up == KEYBOARD_Enter == 0x100
> >
> > Ideally for joystick emulation it would be more natural for the user
> > to choose native keys but that's not what the dialog shows.
> >
> > Berto

Re: [fuse-emulator-devel] game : Three Weeks in Paradise

[Adam S. <sul...@gm...>]

Hello Alberto.

Thank  you very much for your help.

I followed your directions and it did help me.

However it seems that the command line options are not preserved when
saving and then restoring snapshot. After the restore the keys does
not work anymore.

PS: What extension should have the snapshot files ?

Sincerely,
Adam Sulmicki

On 10/26/21, Alberto Garcia <be...@ig...> wrote:
> On Tue, Oct 26, 2021 at 05:50:21AM +0200, Adam Sulmicki wrote:
>> I am trying to play : Three Weeks in Paradise
>>
>> https://www.worldofspectrum.org//pub/sinclair/games/t/ThreeWeeksInParadise128(different).tzx.zip
>>
>> I can't seem to get arrow keys working in the game. Any help?
>
> Hi!
>
> This list is for discussions about the development of the emulator,
> not about general usage. You can use the Help forums for that:
> https://sourceforge.net/p/fuse-emulator/discussion/
>
> But I think we actually have a bug, so I'll take the opportunity to
> share the details :-)
>
> First, the answer for your question:
>
> Three Weeks in Paradise does not support the cursor keys or cursor
> joystick, but you can emulate a joystick using your computer's arrow
> keys:
>
> $ fuse --kempston --joystick-keyboard-output 2 --joystick-keyboard-up 256
> --joystick-keyboard-down 257 --joystick-keyboard-left 258
> --joystick-keyboard-right 259 --joystick-keyboard-fire 32 -m 128
> ThreeWeeksInParadise.tzx
>
> Once the game is loaded, select "2. KEMPSTON" from the game menu. The
> controls are the arrow keys and space to jump.
>
> Now, for the rest of the team:
>
> The "Configure joystick" dialog allows mapping Spectrum keys (enum
> keyboard_key_name) to the joystick controls but then the native keys
> (enum input_key) are the ones actually used.
>
> Two ways to see that:
>
> 1) Emulate a cursor joystick and use code 274 (INPUT_KEY_F8) for the
>    fire button:
>
>    $ fuse --joystick-keyboard-output 1 --joystick-keyboard-fire 274
>
>    Press F8 and you'll see joystick fire ("0") on the screen, although
>    F8 is not a Spectrum key.
>
> 2) Open Options -> Joysticks -> Keyboard, select "Cursor" type and
>    Button for FIRE -> Enter.
>
>    Now if you press ENTER you should see joystick fire ("0"). Instead
>    you'll only see that if you press Arrow Up.
>
>    And this is because INPUT_KEY_Up == KEYBOARD_Enter == 0x100
>
> Ideally for joystick emulation it would be more natural for the user
> to choose native keys but that's not what the dialog shows.
>
> Berto
>
>
> _______________________________________________
> fuse-emulator-devel mailing list
> fus...@li...
> https://lists.sourceforge.net/lists/listinfo/fuse-emulator-devel
>

Re: [fuse-emulator-devel] game : Three Weeks in Paradise

[Alberto G. <be...@ig...>]

On Tue, Oct 26, 2021 at 05:50:21AM +0200, Adam Sulmicki wrote:
> I am trying to play : Three Weeks in Paradise
> 
> https://www.worldofspectrum.org//pub/sinclair/games/t/ThreeWeeksInParadise128(different).tzx.zip
> 
> I can't seem to get arrow keys working in the game. Any help?

Hi!

This list is for discussions about the development of the emulator,
not about general usage. You can use the Help forums for that:
https://sourceforge.net/p/fuse-emulator/discussion/

But I think we actually have a bug, so I'll take the opportunity to
share the details :-)

First, the answer for your question:

Three Weeks in Paradise does not support the cursor keys or cursor
joystick, but you can emulate a joystick using your computer's arrow
keys:

$ fuse --kempston --joystick-keyboard-output 2 --joystick-keyboard-up 256 --joystick-keyboard-down 257 --joystick-keyboard-left 258 --joystick-keyboard-right 259 --joystick-keyboard-fire 32 -m 128 ThreeWeeksInParadise.tzx

Once the game is loaded, select "2. KEMPSTON" from the game menu. The
controls are the arrow keys and space to jump.

Now, for the rest of the team:

The "Configure joystick" dialog allows mapping Spectrum keys (enum
keyboard_key_name) to the joystick controls but then the native keys
(enum input_key) are the ones actually used.

Two ways to see that:

1) Emulate a cursor joystick and use code 274 (INPUT_KEY_F8) for the
   fire button:

   $ fuse --joystick-keyboard-output 1 --joystick-keyboard-fire 274

   Press F8 and you'll see joystick fire ("0") on the screen, although
   F8 is not a Spectrum key.

2) Open Options -> Joysticks -> Keyboard, select "Cursor" type and
   Button for FIRE -> Enter.

   Now if you press ENTER you should see joystick fire ("0"). Instead
   you'll only see that if you press Arrow Up.

   And this is because INPUT_KEY_Up == KEYBOARD_Enter == 0x100

Ideally for joystick emulation it would be more natural for the user
to choose native keys but that's not what the dialog shows.

Berto

[fuse-emulator-devel] game : Three Weeks in Paradise

[Adam S. <sul...@gm...>]

Hello,

I am trying to play : Three Weeks in Paradise

https://www.worldofspectrum.org//pub/sinclair/games/t/ThreeWeeksInParadise128(different).tzx.zip

I can't seem to get arrow keys working in the game. Any help?

I mean I would like to be able to use cursor keys on my keyboard to
control character.

I am using

fuse-emulator-1.5.7-4.fc34.x86_64
Linux Fedora 34

[fuse-emulator-devel] gdbserver support

[desertkun <des...@gm...>]

Hello.

I have opened a merge request which will add a new feature to fuse:
gdbserver
https://sourceforge.net/p/fuse-emulator/fuse/merge-requests/9/

This change allows Fuse to be debuggable on *source level*. Thus, compiler
toolchains that can understand gdb protocol, could connect to Fuse and
properly inspect it. For example, z88dk, a rather popular compiler for the
zx spectrum, has a tool, z88dk-gdb, which is compatible with this.

Session example:
[image: pppppppp.png]

I've spent some time on polishing this, so this is pretty much ready to go
as is. However, should you have any questions, please let me know.

Regards.

Re: [fuse-emulator-devel] W5100 emulation in Fuse

[Andrea <mar...@gm...>]

On 29/04/2021 08:26, Alex Badea wrote:
> Hi,
> 
> On Wed, Apr 28, 2021 at 8:14 AM Andrea <mar...@gm...> wrote:
>>
>> On 28/04/2021 15:12, Alan Cox wrote:
>>> Take a look at
>>>
>>> https://github.com/kvmtool/kvmtool/tree/master/net/uip
> 
> Another one (which is used by e.g. qemu) is
> https://gitlab.freedesktop.org/slirp/libslirp
> 
> Cheers,
> Alex
> 
This is a fantastic suggestion.
Thank you

Re: [fuse-emulator-devel] W5100 emulation in Fuse

[Alex B. <vam...@gm...>]

Hi,

On Wed, Apr 28, 2021 at 8:14 AM Andrea <mar...@gm...> wrote:
>
> On 28/04/2021 15:12, Alan Cox wrote:
> > Take a look at
> >
> > https://github.com/kvmtool/kvmtool/tree/master/net/uip

Another one (which is used by e.g. qemu) is
https://gitlab.freedesktop.org/slirp/libslirp

Cheers,
Alex

Re: [fuse-emulator-devel] W5100 emulation in Fuse

[Alan C. <al...@ll...>]

On Tue, 27 Apr 2021 08:21:14 +0100
Andrea <mar...@gm...> wrote:

> I see FUSE has a W5100 Ethernet card emulation
> 
> https://sourceforge.net/p/fuse-emulator/fuse/ci/master/tree/peripherals/nic/w5100_socket.c
> 
> I am writing an emulation for this card for AppleWin (Uthernet 2).
> 
> I have a POC and was trying to understand if I could use the one from fuse.
> I noticed the following difference:
> 
> fuse emulates udp and tcp, while I need ipraw and macraw.
> 
> So I did my homework and got them working.
> But I then hit a few issues and wanted to understand how you solved them
> 
> - raw sockets require privileged access (annoying)
> - impossible to forward udp packets for dhcp (root or no root).
> 
> The problem with udp packets is that I need to listen on port 67-udp and this is impossible because 
> it is already taken by dnsmasqd on my system.
> 
> So this is the question I have for you: have you got any example of a ZX80 software that does DHCP 
> and this works with your W5100 emulation?
> If yes, I am really curious to see how you did it.
> 
> I have a solution, but it is a huge effort, where I intercept DHCP, reply wit a dummy (10.0.0.1) and 
> then forward udp and tcp packets (a la NAT)
> I think this is what VirtualBox does.

Take a look at

https://github.com/kvmtool/kvmtool/tree/master/net/uip

It's a dead project now but the uip code in it turns a raw network
connection into host tcp, udp etc. You'd still probably need the DHCP
proxy in there but it should let you turn macraw into host sockets for at
least the simple stacks used on micros. There is a much better version of
the code in very old versions of the Intel clear containers but I've no
idea where you'd dig that out on the net any more.

Another bizarre but effective approach is to make your emulator one end
of a simple VPN/IPIP tunnel instead and run the server end somewhere.

Alan