You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(88) |
Nov
(58) |
Dec
(53) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(35) |
Feb
(43) |
Mar
(89) |
Apr
(54) |
May
(32) |
Jun
(36) |
Jul
(121) |
Aug
(40) |
Sep
(8) |
Oct
(55) |
Nov
(52) |
Dec
(36) |
2005 |
Jan
(68) |
Feb
(91) |
Mar
(24) |
Apr
(77) |
May
(31) |
Jun
(3) |
Jul
(3) |
Aug
(22) |
Sep
(35) |
Oct
(10) |
Nov
(6) |
Dec
(9) |
2006 |
Jan
(10) |
Feb
(3) |
Mar
(2) |
Apr
(1) |
May
(6) |
Jun
(8) |
Jul
(61) |
Aug
(54) |
Sep
(12) |
Oct
(7) |
Nov
(6) |
Dec
(9) |
2007 |
Jan
(37) |
Feb
(61) |
Mar
(66) |
Apr
(90) |
May
(197) |
Jun
(130) |
Jul
(112) |
Aug
(79) |
Sep
(41) |
Oct
(55) |
Nov
(107) |
Dec
(53) |
2008 |
Jan
(38) |
Feb
(35) |
Mar
(105) |
Apr
(26) |
May
(41) |
Jun
(74) |
Jul
(20) |
Aug
(29) |
Sep
(12) |
Oct
(51) |
Nov
(79) |
Dec
(41) |
2009 |
Jan
(52) |
Feb
(34) |
Mar
(58) |
Apr
(20) |
May
(24) |
Jun
(53) |
Jul
(20) |
Aug
(17) |
Sep
(25) |
Oct
(63) |
Nov
(29) |
Dec
(14) |
2010 |
Jan
(22) |
Feb
(8) |
Mar
(5) |
Apr
(4) |
May
(25) |
Jun
(11) |
Jul
(6) |
Aug
(14) |
Sep
(31) |
Oct
(40) |
Nov
(10) |
Dec
(76) |
2011 |
Jan
(122) |
Feb
(47) |
Mar
(27) |
Apr
(108) |
May
(32) |
Jun
(42) |
Jul
(21) |
Aug
(12) |
Sep
(22) |
Oct
(2) |
Nov
(17) |
Dec
(17) |
2012 |
Jan
(85) |
Feb
(55) |
Mar
(28) |
Apr
(16) |
May
(38) |
Jun
(44) |
Jul
(40) |
Aug
(23) |
Sep
(23) |
Oct
(36) |
Nov
(21) |
Dec
(78) |
2013 |
Jan
(45) |
Feb
(20) |
Mar
(4) |
Apr
(6) |
May
(65) |
Jun
(32) |
Jul
|
Aug
|
Sep
(4) |
Oct
(8) |
Nov
(12) |
Dec
|
2014 |
Jan
(3) |
Feb
(5) |
Mar
(10) |
Apr
|
May
|
Jun
(5) |
Jul
(4) |
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
2015 |
Jan
|
Feb
(1) |
Mar
(40) |
Apr
(31) |
May
(171) |
Jun
(45) |
Jul
|
Aug
(1) |
Sep
(2) |
Oct
(13) |
Nov
(6) |
Dec
(6) |
2016 |
Jan
|
Feb
|
Mar
(23) |
Apr
(12) |
May
(56) |
Jun
(57) |
Jul
(39) |
Aug
(8) |
Sep
(13) |
Oct
(35) |
Nov
(28) |
Dec
(6) |
2017 |
Jan
(12) |
Feb
(7) |
Mar
(8) |
Apr
(7) |
May
(5) |
Jun
(22) |
Jul
(9) |
Aug
(27) |
Sep
(19) |
Oct
(10) |
Nov
(11) |
Dec
(8) |
2018 |
Jan
(11) |
Feb
(25) |
Mar
(6) |
Apr
(6) |
May
(2) |
Jun
(20) |
Jul
(9) |
Aug
(7) |
Sep
(12) |
Oct
|
Nov
(3) |
Dec
(17) |
2019 |
Jan
(7) |
Feb
(10) |
Mar
(5) |
Apr
(2) |
May
(1) |
Jun
|
Jul
(5) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
(7) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
2021 |
Jan
(1) |
Feb
(26) |
Mar
(8) |
Apr
(7) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(4) |
Nov
(7) |
Dec
|
2022 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
(3) |
Dec
|
2023 |
Jan
|
Feb
|
Mar
(1) |
Apr
(7) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
(5) |
Feb
(3) |
Mar
(8) |
Apr
(5) |
May
(5) |
Jun
(3) |
Jul
|
Aug
(1) |
Sep
(4) |
Oct
(4) |
Nov
|
Dec
|
2025 |
Jan
(1) |
Feb
(4) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Fredrick M. <fr...@sp...> - 2021-02-20 12:01:03
|
Hi Sergio, > On 20 Feb 2021, at 22:42, Sergio Baldoví <ser...@gm...> wrote: > > Have you had a chance to review bug #369? > > I can't review it technically but saving to tape work better with it. Thanks for reminding me about this. I’ll need to have another look at the TZX spec and friends as last edges are something of a headache if I recall correctly. I think we’d also want to add a regression test about this issue too to document the behaviour. Fred |
From: Sergio B. <ser...@gm...> - 2021-02-20 11:42:44
|
Hi Fred, On 3/2/21 14:04, Fredrick Meunier wrote: > Berto: I will also have a look at the fixes you have highlighted (probably by the end of the week). Have you had a chance to review bug #369? I can't review it technically but saving to tape work better with it. Cheers, Sergio |
From: Fredrick M. <fr...@sp...> - 2021-02-13 09:31:54
|
> On 13 Feb 2021, at 17:28, Sergio Baldoví <ser...@gm...> wrote: > > I've also run abi-compliance-checker and get a 100% compatibility (see > attachment). > > The main difference is that I run it on the installed libspectrum tree > [1][2] rather than the build tree, so I guess that it only takes into > account public headers/interfaces. Thanks, while I was also running from a install trees rather than a build tree, I needed to specify the -public-headers option to get the same results as you did. > Honestly I'm not sure about the scope of these changes so I'm happy to > keep your choice. > > I'll also commit patch #411 to benefit from this choice. Happy to take the opportunity to lost binary compatibility here as its not like we are evolving the interface too fast! Fred |
From: Sergio B. <ser...@gm...> - 2021-02-13 06:28:19
|
Hi Fred, On 12/2/21 12:43, Fredrick Meunier wrote: >> On 12 Feb 2021, at 17:41, Sergio Baldoví <ser...@gm...> wrote: >> >> Do you think a soname dump is required? >> >> I was expecting an increase of the age value too. > > Hmm I did do an api compatibility check to decide on the appropriate values (see attached) and it reported that both source and binary compatibility has been affected by the changes. > > The source isn’t 100% compatible due to the removal of libspectrum_snap_alloc_internal() which isn’t supposed to be part of the public API but is still being flagged. > > Binary compatibility is affected by the changes to the libspectrum_snap structure.so its a deliberate choice to not bump the age value. > > Have I made a mistake? I've also run abi-compliance-checker and get a 100% compatibility (see attachment). The main difference is that I run it on the installed libspectrum tree [1][2] rather than the build tree, so I guess that it only takes into account public headers/interfaces. Honestly I'm not sure about the scope of these changes so I'm happy to keep your choice. I'll also commit patch #411 to benefit from this choice. Cheers, Sergio [1] https://sourceware.org/glibc/wiki/Testing/ABI_checker [2] https://fedoraproject.org/wiki/How_to_check_for_ABI_changes_with_abi_compliance_checker |
From: Fredrick M. <fr...@sp...> - 2021-02-12 11:44:06
|
Hi Sergio, > On 12 Feb 2021, at 17:41, Sergio Baldoví <ser...@gm...> wrote: > > On 11/2/21 12:05, fredm--- via fuse-emulator-cvs wrote: >> ## * Always increase the revision value. >> ## * Increase the age value only if the changes made to the ABI are backward >> ## compatible. >> -libspectrum_la_LDFLAGS = -version-info 16:14:8 -no-undefined @WINDRES_LDFLAGS@ >> +libspectrum_la_LDFLAGS = -version-info 17:15:8 -no-undefined @WINDRES_LDFLAGS@ > > Do you think a soname dump is required? > > I was expecting an increase of the age value too. Hmm I did do an api compatibility check to decide on the appropriate values (see attached) and it reported that both source and binary compatibility has been affected by the changes. The source isn’t 100% compatible due to the removal of libspectrum_snap_alloc_internal() which isn’t supposed to be part of the public API but is still being flagged. Binary compatibility is affected by the changes to the libspectrum_snap structure.so its a deliberate choice to not bump the age value. Have I made a mistake? Fred [1] Compatibility report, X is 1.4.4 and Y is the proposed 1.5.0 |
From: Sergio B. <ser...@gm...> - 2021-02-12 06:41:32
|
Hi Fred, On 11/2/21 12:05, fredm--- via fuse-emulator-cvs wrote: > diff --git a/Makefile.am b/Makefile.am > index 55128b6..4d47afc 100644 > --- a/Makefile.am > +++ b/Makefile.am > @@ -76,7 +76,7 @@ endif > ## * Always increase the revision value. > ## * Increase the age value only if the changes made to the ABI are backward > ## compatible. > -libspectrum_la_LDFLAGS = -version-info 16:14:8 -no-undefined @WINDRES_LDFLAGS@ > +libspectrum_la_LDFLAGS = -version-info 17:15:8 -no-undefined @WINDRES_LDFLAGS@ > > libspectrum_la_LIBADD = @AUDIOFILE_LIBS@ @GLIB_LIBS@ -lm > Do you think a soname dump is required? I was expecting an increase of the age value too. Cheers, Sergio |
From: Fredrick M. <fr...@sp...> - 2021-02-08 11:31:32
|
> On 4 Feb 2021, at 00:04, Fredrick Meunier <fr...@sp...> wrote: > > OK, I’ll plan to do a release essentially of the master branch soon then. Just an update - I have spent my time getting my release scripts and environments back up to date. Still working on it, maybe more news this weekend. Fred |
From: Sergio B. <ser...@gm...> - 2021-02-03 23:05:26
|
Hi Alistair, On 3/2/21 14:18, Alistair wrote: > Presumably my teletext stuff wouldn't be considered stable at this point > since it was never merged into master. [1] > What do I still need to do to get it included in time for 1.5.9 (or > whatever)? Actually ttx2000s code was merged at September 2020, so it will be released soon. It lacks snapshot support, though. Cheers, Sergio |
From: Alistair <ali...@zx...> - 2021-02-03 13:38:16
|
On 2021-02-03 13:04, Fredrick Meunier wrote: >> On 2 Feb 2021, at 10:39, Sergio Baldoví <ser...@gm...> wrote: >>> Assuming that things are in a stable state on the main branch, it would help if the Changelogs in libspectrum, fuse-utils and fuse are up to date for the changes since the last release. >> >> The master branch is quite stable but ChangeLogs need a review. > > OK, I’ll plan to do a release essentially of the master branch soon then. Presumably my teletext stuff wouldn't be considered stable at this point since it was never merged into master. [1] What do I still need to do to get it included in time for 1.5.9 (or whatever)? Alistair. [1] This is probably good in some ways, because the data stream format might change to something less hacky soon if a bunch of other procrastinated projects occur in a cascading fashion. |
From: Fredrick M. <fr...@sp...> - 2021-02-03 13:05:04
|
> On 2 Feb 2021, at 10:39, Sergio Baldoví <ser...@gm...> wrote: > > Hi Fred & Berto, > > On 1/2/21 12:02, Fredrick Meunier wrote: >> I wasn’t able to put much effort into Fuse over the last couple of years but would be happy to go through the release process to get an update out. > > I haven't got much free time lately but I can help with the win32 version. Thanks! >> Assuming that things are in a stable state on the main branch, it would help if the Changelogs in libspectrum, fuse-utils and fuse are up to date for the changes since the last release. > > The master branch is quite stable but ChangeLogs need a review. OK, I’ll plan to do a release essentially of the master branch soon then. Berto: I will also have a look at the fixes you have highlighted (probably by the end of the week). Thanks, Fred |
From: Sergio B. <ser...@gm...> - 2021-02-01 23:39:32
|
Hi Fred & Berto, On 1/2/21 12:02, Fredrick Meunier wrote: > I wasn’t able to put much effort into Fuse over the last couple of years but would be happy to go through the release process to get an update out. I haven't got much free time lately but I can help with the win32 version. > Assuming that things are in a stable state on the main branch, it would help if the Changelogs in libspectrum, fuse-utils and fuse are up to date for the changes since the last release. The master branch is quite stable but ChangeLogs need a review. Cheers, Sergio |
From: Alberto G. <be...@ig...> - 2021-02-01 13:07:17
|
On Mon, Feb 01, 2021 at 10:02:40PM +1100, Fredrick Meunier wrote: > > I was wondering if there are any plans for Fuse 1.5.8 ? Is there > > any blocker, or anything that needs help? > > I wasn’t able to put much effort into Fuse over the last couple of > years but would be happy to go through the release process to get an > update out. There are also a few fixes for tape loading bugs that need review (not necessarily for this release if there is no time). This was reported by a user and is easy to reproduce: https://sourceforge.net/p/fuse-emulator/bugs/369/ These are technically valid TZX files but probably not easy to see in real life. The fixes are simple, however: https://sourceforge.net/p/fuse-emulator/bugs/444/ https://sourceforge.net/p/fuse-emulator/bugs/445/ https://sourceforge.net/p/fuse-emulator/bugs/458/ This is a fix for a well-known bug that causes loading errors with MASK, Lone Wolf 3, Basil and possibly others, but it's a bit of a bigger change: https://sourceforge.net/p/fuse-emulator/bugs/431/?page=1&limit=25#f102 Berto |
From: Fredrick M. <fr...@sp...> - 2021-02-01 11:21:39
|
Hi Berto, Sent from my iPad > On 1 Feb 2021, at 05:48, Alberto Garcia <be...@ig...> wrote: > > I was wondering if there are any plans for Fuse 1.5.8 ? Is there any > blocker, or anything that needs help? I wasn’t able to put much effort into Fuse over the last couple of years but would be happy to go through the release process to get an update out. Assuming that things are in a stable state on the main branch, it would help if the Changelogs in libspectrum, fuse-utils and fuse are up to date for the changes since the last release. Phil: are you still in a position to sign the release tarballs? Thanks, Fred |
From: Alberto G. <be...@ig...> - 2021-01-31 18:48:24
|
Hi, Fuse 1.5.7 was released a bit more than 2 years ago, and there hasn't been any new release since then. There are more than new 80 commits in the git repository, some of them fixes for known bugs, and also a bunch of patches in the bug tracker waiting to be reviewed and/or applied. I was wondering if there are any plans for Fuse 1.5.8 ? Is there any blocker, or anything that needs help? Regards, Berto |
From: Szász G. <sz...@hu...> - 2020-12-07 18:30:35
|
On Mon, Dec 07, 2020 at 01:14:54PM +0100, Niccolo Rigacci wrote: > After several years of oblivion I revived my ZX-Spectrum software > files. In the '90s I purchased an emulator by Gerton Lunter > (great sofware for the MS-DOS!), but today I installed Fuse GTK > on my Linux box. > > It turned out that the serial files that I saved with the old > emulator does not load in Fuse. If I try to load a BASIC program > with > > LOAD *"b" > > I get the error: > > Wrong file type, 0:1 > > After some hours of hunting, I discovered that adding an 0x2A > byte after every 0x00 byte into the stream solved the problem. > > Why is that required? > > Is the serial format handled directly by Fuse or is it handled > via libspectrum? > > Btw, a big thank you to everyone who made this software! > Hello Niccolo, The serial (RS232) 'stream' is not just a plain byte stream of sended/received bytes, because RS232 has some handshake mechanism to synchronise the receiver and the sender machines. ZX spectrum uses only 4 lines to communicate: DTR, CTS, TX, RX I cannot blah-blah because you can found a lot of detailed description about RS232 on the net... if you interested ever ;-) ------ We can try to emulate the handshake stuff, so we connect two fuse with named pipes over RS232, and it works well. We use escape sequencies to insert handshake information into byte stream: 0 0 -> DTR goes low 0 1 -> DTR goes high 0 2 -> CTS goes low 0 3 -> CTS goes high 0 42 -> real 0 So 0 byte is the escape character and you emit a real 0 byte if you send a 0 and 42 (*) in hex 0x2a And yes, if you have a bare stream of bytes from an RS232 communication you have to change every 0x00 with 0x00 0xa2 Here is some description from if1.c file: RS232: DTR -> Data Terminal Ready (DTE -> DCE) CTS -> Clear To Send (DCE -> DTE) TX -> Transmitted Data (DTE -> DCE) RX -> Received Data (DCE -> DTE) The IF1 serial behaves not as a DTE (Data Terminal Equipment, e.g. a computer) but as a DCE (Data Communications Equipment, e.g. a modem) If we were to consider the ZX Spectrum a DTE, we would rename the lines: DTR := DSR (Data Set Ready) CTS := RTS (Request To Send) TX := RX RX := TX On the communication channels: Bytes interpreted as is, except: 0x00 0x00 --> DTR ~~\__ 0x00 0x01 --> DTR __/~~ 0x00 0x02 --> CTS ~~\__ 0x00 0x03 --> CTS __/~~ 0x00 ? --> lost 0x00 * --> 0x00 Additionally: if fuse read 0x00 0x00 => DTR = 0 ~~\__ if fuse read 0x00 0x01 => DTR = 1 __/~~ if CTS = ~~\__ fuse send 0x00 0x02 if CTS = __/~~ fuse send 0x00 0x03 if fuse lost send 0x00 + 0x3f (?) every other 0x00 + 0x## are discarded Best regards, Gergely |
From: Niccolo R. <ni...@ri...> - 2020-12-07 12:34:30
|
After several years of oblivion I revived my ZX-Spectrum software files. In the '90s I purchased an emulator by Gerton Lunter (great sofware for the MS-DOS!), but today I installed Fuse GTK on my Linux box. It turned out that the serial files that I saved with the old emulator does not load in Fuse. If I try to load a BASIC program with LOAD *"b" I get the error: Wrong file type, 0:1 After some hours of hunting, I discovered that adding an 0x2A byte after every 0x00 byte into the stream solved the problem. Why is that required? Is the serial format handled directly by Fuse or is it handled via libspectrum? Btw, a big thank you to everyone who made this software! -- Niccolo Rigacci - http://www.rigacci.net/ Firenze/Prato - Italy Tel. Mobile: +39-327-5619352 |
From: Alistair <ali...@zx...> - 2020-07-05 19:59:41
|
What if anything do I still need to do to get this merged into the next release? At least three people have actually shown an interest in the existence of the teletext adapter since I wrote the code ;D Alistair. |
From: Szász G. <sz...@hu...> - 2020-06-29 22:10:01
|
Hello Javier, First of all, the FDD/FDC emulation is not perfect in fuse at now. e.g. the timings of FORMAT is awful, or the timings of READ/WRITE sectors is far from perfect (there is no real emulation of disk rotation). The WD1770/WD1772 differ only in disk drive stepping rates. The FDC wait for this time after send a STEP pulse to the FDD. So it only can cause trouble, if your FDD cannot move its head so short time across cylinders... So if you use change the WD1772 to WD1770 IMHO you not need to change the firmware, because with the same code the WD1770 uses longer stepping times than the WD1772. In the (implemented) emulation there is no important rule of the stepping rates (how much time needed by the drive to move the head to the next cylinder), so there is no practical difference the stepping rates, or the two stepping rates presets. Hmmm... the wrong stepping rates came from the ATARI ST sources https://github.com/ggnkua/Atari_ST_Sources/blob/master/Docs/WD1772.TXT and later I didnt take care about it. Best regards, Gergely Szász On Fri, Jun 26, 2020 at 10:16:25AM +0100, Philip Kendall wrote: > [ Forwarding to the list with Javier's permission ] > > ---------- Forwarded message --------- > From: Javier Herrera <[1]jav...@ya...> > Date: Thu, Jun 25, 2020 at 12:37 PM > Subject: About WD1772/WD1770 emulation in Fuse > To: [2]phi...@sh... <[3]phi...@sh...> > > Hello Phillip. > I'm a Spanish enthusiastic of the ZX Spectrum and I have been looking for > some information about the PlusD interface, in order to modify the > firmware in order to replace the original WD1772 FDC with the WD1770 FDC > successfully, because the different step timmings. Finally I remembered > that your Spectrum emulator Fuse implements such as disk interface and I > thought maybe your fuse sources (wd_fdc.h, wd_fdc.c, plusd.h and plusd.c) > could be useful. > Two things have stood me out in your sources: > - The WD1770 in wd_type_t is always used instead WD1772, when called > wd_fdc_alloc_fdc. Why? > - Inside this function, rates for the WD1770 are initialized to 6, 12, 20 > and 20 ms, whereas rates are 2, 3, 5 and 6 ms for the WD1772. Is this OK? > Because looking for the WD1772 FDC specs, I've found that the rates are 6, > 12, 2 and 3 ms (I mean, they are in a different order). > Could you explain something about these two questions? Thank you in > advance. > Best regards, > Javier Herrera > > Links: > 1. mailto:jav...@ya.../ > 2. mailto:phi...@sh.../ > 3. mailto:phi...@sh.../ > _______________________________________________ > fuse-emulator-devel mailing list > fus...@li... > https://lists.sourceforge.net/lists/listinfo/fuse-emulator-devel |
From: Philip K. <ph...@sh...> - 2020-06-26 09:16:43
|
[ Forwarding to the list with Javier's permission ] ---------- Forwarded message --------- From: Javier Herrera <jav...@ya...> Date: Thu, Jun 25, 2020 at 12:37 PM Subject: About WD1772/WD1770 emulation in Fuse To: phi...@sh... <phi...@sh...> Hello Phillip. I'm a Spanish enthusiastic of the ZX Spectrum and I have been looking for some information about the PlusD interface, in order to modify the firmware in order to replace the original WD1772 FDC with the WD1770 FDC successfully, because the different step timmings. Finally I remembered that your Spectrum emulator Fuse implements such as disk interface and I thought maybe your fuse sources (wd_fdc.h, wd_fdc.c, plusd.h and plusd.c) could be useful. Two things have stood me out in your sources: - The WD1770 in wd_type_t is always used instead WD1772, when called wd_fdc_alloc_fdc. Why? - Inside this function, rates for the WD1770 are initialized to 6, 12, 20 and 20 ms, whereas rates are 2, 3, 5 and 6 ms for the WD1772. Is this OK? Because looking for the WD1772 FDC specs, I've found that the rates are 6, 12, 2 and 3 ms (I mean, they are in a different order). Could you explain something about these two questions? Thank you in advance. Best regards, Javier Herrera |
From: Cesare F. <wal...@gm...> - 2020-06-05 11:34:32
|
Il giorno ven 5 giu 2020 alle ore 12:55 Alberto Garcia <be...@ig...> ha scritto: > You're right, although in this case I'm the one packaging Fuse for > Debian and as far as I can see Ubuntu is using those exact same > packages. Yes, that's it. :-) I'm an Ubuntu packager (mainly Mame these days). We only diverge from Debian if there's a real good reason. The Ubuntu tree is synced with testing roughly at the end of each release cycle, when freeze starts and only fixing is allowed. Cesare |
From: Alberto G. <be...@ig...> - 2020-06-05 10:54:43
|
On Fri, Jun 05, 2020 at 01:55:56AM +0100, Alan Cox wrote: > > are you going to answer me or sort out this issue? > > If you got an ubuntu update through ubuntu that broke stuff shipped > by Ubuntu you need to file bugs with Ubuntu - they will actually > have some idea what they shipped, how they configured it and why > their version isn't working now. You're right, although in this case I'm the one packaging Fuse for Debian and as far as I can see Ubuntu is using those exact same packages. I suppose he's simply not subscribed to this mailing list, I just sent him a private message. Berto |
From: Pedro T. <pe...@de...> - 2020-06-05 09:43:51
|
Did you try what Alberto Garcia suggested? Also, using Ubuntu 20.04 here, with its included Fuse, and everything works fine. On 04/06/2020 19:35, Darren Chambers wrote: > are you going to answer me or sort out this issue? > > > On Fri, 29 May 2020 at 17:21, Darren Chambers > <dar...@gm... > <mailto:dar...@gm...>> wrote: > > This is the error that I now encounter after the last auto update. > > This program is distributed in the hope that it will be useful, > but WITHOUT ANY WARRANTY; without even the implied warranty of > MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the > GNU General Public License for more details. > > fuse: error: This machine does not support the Interface 2 > fuse: error initialising -- giving up! > > I have tried the fuse --no-interface2 command and it still tells > me there is no support for interface 2. I have tried other > emulators that use interface 2 and have had no problems. Fuse is > the best emulator I have used and now its not working. Please advise > > > > _______________________________________________ > fuse-emulator-devel mailing list > fus...@li... > https://lists.sourceforge.net/lists/listinfo/fuse-emulator-devel |
From: Alan C. <al...@ll...> - 2020-06-05 01:36:33
|
On Thu, 4 Jun 2020 19:35:21 +0100 Darren Chambers <dar...@gm...> wrote: > are you going to answer me or sort out this issue? If you got an ubuntu update through ubuntu that broke stuff shipped by Ubuntu you need to file bugs with Ubuntu - they will actually have some idea what they shipped, how they configured it and why their version isn't working now. Alan |
From: Darren C. <dar...@gm...> - 2020-06-04 18:35:39
|
are you going to answer me or sort out this issue? On Fri, 29 May 2020 at 17:21, Darren Chambers < dar...@gm...> wrote: > This is the error that I now encounter after the last auto update. > > This program is distributed in the hope that it will be useful, > but WITHOUT ANY WARRANTY; without even the implied warranty of > MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the > GNU General Public License for more details. > > fuse: error: This machine does not support the Interface 2 > fuse: error initialising -- giving up! > > I have tried the fuse --no-interface2 command and it still tells me there > is no support for interface 2. I have tried other emulators that use > interface 2 and have had no problems. Fuse is the best emulator I have used > and now its not working. Please advise > |
From: Alberto G. <be...@ig...> - 2020-05-30 12:18:03
|
On Fri, May 29, 2020 at 05:21:07PM +0100, Darren Chambers wrote: > fuse: error: This machine does not support the Interface 2 > fuse: error initialising -- giving up! > > I have tried the fuse --no-interface2 command and it still tells me > there is no support for interface 2. I have tried other emulators > that use interface 2 and have had no problems. Fuse is the best > emulator I have used and now its not working. Please advise Perhaps Fuse is trying to load an Interface 2 cartridge but the IF2 support is not enabled. Try running 'fuse --interface2', or simply open your ~/.fuserc file and check the status of the <interface2> and <if2cart> settings. Berto |