Page 42 of 51
Re: compatibility
Posted: Fri 08 Jun 2018, 07:43
by mistfire
Volhout wrote:Dear mistfire,
Just an observation:
I personally expect that Slim will be used because it is
a/ slim (on small applications / systems / older systems).
b/ the clean windows NT appearance (personal preference).
In my perspective it is doubtfull if the person using Slim would sacrifice 20-30% performance to gain robustness against Spectre/Meltdown.
Question:
I do have a question though with repect to compatibility of Slim.
I have seen that like 50% of the PET's and SFSés simply don't work on Slim. With a varietey of error messages if started from commandline.
Or the behaviour is very different. (i.e. Pwidgets, that seems to live UNDER the desktop, and sometimes peep through).
Is there a way to improve compatibility with puppy, whilst maintaining the Slim way of working. Maybe the trimming in Slim has removed packages others rely on.
i.e. Take the full XSlacko, and apply some patches. Is this achievable ?
I currently maintain 3 puppy distro's because of this. Besides Slim, an older puppy, and a newer one. And one Slim (not so slim anymore) would suffice....?
Regarsds,
Volhout
May I know what SFS files and PET's that does not work?
mouseclick and delay in response
Posted: Sun 10 Jun 2018, 07:01
by hamoudoudou
mouseclick and delay in response : it looks like mouse disconnect and reconnect (with audio jingle) both in x-slim slacko and tazpup...
How could it be repaired
PS : are users blacklisted in tazpup ? only geeks get answers.. That is why i ask here, in slim x-slacko.
Sorry, only Mistfire give answers
Posted: Mon 11 Jun 2018, 00:31
by mistfire
@hamoudoudou sorry for the long delay. Check your usb ports first make sure that it was clean (a shot of contact cleaner will help). Check if the usb port holds usb devices firmly. Make sure that your mouse does not loose connection.
Posted: Mon 11 Jun 2018, 08:41
by Volhout
Hi mistfire,
About the compatibility with SFS's and PET's.
http://murga-linux.com/puppy/viewtopic. ... 73&t=87503
That is the one that I tried and did not work, and drove me to write the question. It works on tahr605, slacko57, but not on slim.
But Also: KiCAD 4.02 from PPM, I think I can find back the list of everything that did not work. And Pwidgets....I would like to have the anaog clock and calendar.
Regards,
Volhout
plug-in recognize, i should look there, i think.
Posted: Thu 14 Jun 2018, 12:00
by hamoudoudou
about yr answer received. screenshot added above.. No urgency. I think problem is software because only with midori and tzpup x-slim Slacko.
plug-in recognize, i should look there, i think.
Fact is since first versions,
Posted: Fri 15 Jun 2018, 02:56
by mistfire
@hamoudoudou I think it was kernel issue I will wait for another stable kernel release
these connect disconnect could come from
Posted: Fri 15 Jun 2018, 08:20
by hamoudoudou
merci Mistfire, i saw that your will change the kernel.. However i will search from where these connect disconnect could come from. From time to time, i touch 'programing', seldom with success.. using 'méthodes peu orthodoxes'
Dpup Stretch playing now, no trouble with mouse..
What i have to say to be useful helper is that Windows 7 does as Tazpup and X-slim for the mouse usage
I plugged it in different holes, and everywhere the same.
Posted: Sat 16 Jun 2018, 03:55
by mistfire
@hamoudoudou X-Slacko Slim rarely change library files. Instead it change kernel only depending upon the situation.
I have also a suggestion regarding to the mouse. Try also to use other mouse to tell whether it works also or not.
what an evidance ! i do it at once.
Posted: Sat 16 Jun 2018, 07:55
by hamoudoudou
what an evidance ! i do it at once.
Posted: Tue 19 Jun 2018, 02:04
by mistfire
New X-Slacko Slim iteration released
Changes:
* Fatal error on init during full install is fixed
* Some fixes
Download:
https://drive.google.com/file/d/1gFadl8 ... sp=sharing
MD5 Checksum: 888d6d16d41486d5530ad113edf5bbf7
Posted: Tue 19 Jun 2018, 09:11
by Sage
15r: - getting XZ data is corrupt. System Halted.
Re-d/l, re-burn, used 'severe video problems option' boots ~half-way, then KP.
Posted: Mon 25 Jun 2018, 08:36
by mistfire
New X-Slacko Slim iteration released
Changes:
* Linux kernel 4.17.2
* Initial uefi support on probepart
Download: https://drive.google.com/file/d/1K7ychv ... sp=sharing
MD5 Checksum: 60401eda6bb2dac2afc9e5474f7f2cc0
Posted: Mon 25 Jun 2018, 12:39
by Sage
r17: getting a new error message:
vesamenu.c32
not a COM32C image
- any clues?
Re-d/l, re-burn, different machines - always the same error message.
Posted: Mon 25 Jun 2018, 13:19
by smokey01
This is what I get trying to boot in Qemu:
Posted: Mon 25 Jun 2018, 16:35
by Sage
This is what I get..
Yup, that's the one.This is what I get. Sadly something seriously going wrong with this dog.
Posted: Mon 25 Jun 2018, 20:14
by Billtoo
Sage wrote:This is what I get..
Yup, that's the one.This is what I get. Sadly something seriously going wrong with this dog.
I downloaded the iso, the md5sum doesn't match what he posted.
# md5sum xslacko-slim-4.4r17.iso
6993833fe9f913c4226e6cf83d665e09 xslacko-slim-4.4r17.iso
#
Posted: Tue 26 Jun 2018, 02:47
by mistfire
There is one answer to that problem. The upload process was corrupted. I wonder why the uploads of X-Slacko Slim got corrupted recently. While TazPup was sucessfully uploaded.
Posted: Tue 26 Jun 2018, 06:53
by Sage
uploads of X-Slacko Slim got corrupted recently
Curious. Perhaps one of our colleagues could assist by mirroring it?
As for md5, never sure whether its the sum that's wrong or the file!
Posted: Wed 27 Jun 2018, 02:00
by mistfire
I'm fixing the issue about file corruption of iso files. I hope I finished it as early as possible
Posted: Sat 30 Jun 2018, 02:22
by mistfire
New X-Slacko iteration released:
* Some bugfixes
Download: https://drive.google.com/file/d/1fyjYdP ... sp=sharing
MD5 Checksum: ff6ad773fa2f370034db2deebaf625a8