X-Slacko Slim 4.4r49 (unique, stable, and flexible)
Maker Tools
mistfire,
I am not sure if this is of any use to you, but I packaged a set of development tools, that works on XSlacko Slim (tested on r54).
http://murga-linux.com/puppy/viewtopic.php?t=111520
I have not tested r55, but will soon
Volhout
I am not sure if this is of any use to you, but I packaged a set of development tools, that works on XSlacko Slim (tested on r54).
http://murga-linux.com/puppy/viewtopic.php?t=111520
I have not tested r55, but will soon
Volhout
Wine SFS
Dear mistfire,
Would it be too much to ask if you can provide a wine SFS tuned for Xslacko Slim including all dependencies.
I spend another evening in trying to combine the Xslacko-14.1 PET and dependencies in and SFS (using all kind of tools like tzx2pet and pet2sfs and petmaker, and failed to succeed. I do get sfs'es, but they simply do not work.
And I do not have the skills to turn this into a working system.
I would really appreciate it !
Volhout
Would it be too much to ask if you can provide a wine SFS tuned for Xslacko Slim including all dependencies.
I spend another evening in trying to combine the Xslacko-14.1 PET and dependencies in and SFS (using all kind of tools like tzx2pet and pet2sfs and petmaker, and failed to succeed. I do get sfs'es, but they simply do not work.
And I do not have the skills to turn this into a working system.
I would really appreciate it !
Volhout
Create Wine.SFS
Hi Volhaut, mistfire,
Have either of you tried dancytron's method: http://murga-linux.com/puppy/viewtopic. ... 226#687226 ?
It should not be necessary to create wine from scratch.
Translation: Install one of version2013's wine pets, perform the steps dancytron laid out, uninstall the pet.
Actually, I'm not sure that method will still work, as is. But the idea is good. I think after installing a wine pet, you'll find a wine binary may have been installed to /usr/bin, or some other "bin" folder. pfind will locate it.
So, after configuring the installed wine, copy /root/.wine + /usr/bin/wine (or wherever) + perhaps any /usr/share/applications/wine_xxx.desktops to a folder named wine and dir2sfs that folder. Then uninstall the wine.pet.
If you have some programs you always run under wine, install them as well before copying /root/.wine. Don't forget to copy any desktop files for them to your build folder.
Alternative-Tested:
I just created a wine.sfs by doing the following.
1. PaDs previously installed: http://murga-linux.com/puppy/viewtopic. ... 359#658359
2. Created a wine-2.16 folder: Right-Click empty space, select new directory, give it the name wine-2.16
3. Downloaded Version2013's wine-2.16 version 2.1 into wine-2.16 folder. Start here & follow links: http://murga-linux.com/puppy/viewtopic. ... 303#968303
Optional 3a. Remember that Version2013 does not include wine menus in his build. If you want wine programs to appear on your Start menu, also download wine_extras-v2.pet from here: https://version2013.yolasite.com/page1.php#wine-misc into the wine-2.16 folder.
4. Right-Click wine-2.16 folder and select "Combine to SFS". Combine to SFS is part of the PaDS application. A wine-2.16.SFS was created in /root.
5. Right-Click wine-2.16.SFS, select SFS-Load. SFS loaded.
6. Open terminal and type --without the quotes-- "wine winecfg". Config ran, installing gecko.
7. Open terminal and typed "wine winefile" -- wine's file-manager opened.
8. Used Linux file-manager to browse to portable-avidemux. Clicked avidemux.exe. Nothing happened.. Right-Clicked empty space and selected "open terminal here". Typed in terminal "wine avidemux.exe". Avidemux opened. Probably "exe" has to be added to "open with" routine.
mikesLr
Have either of you tried dancytron's method: http://murga-linux.com/puppy/viewtopic. ... 226#687226 ?
It should not be necessary to create wine from scratch.
Translation: Install one of version2013's wine pets, perform the steps dancytron laid out, uninstall the pet.
Actually, I'm not sure that method will still work, as is. But the idea is good. I think after installing a wine pet, you'll find a wine binary may have been installed to /usr/bin, or some other "bin" folder. pfind will locate it.
So, after configuring the installed wine, copy /root/.wine + /usr/bin/wine (or wherever) + perhaps any /usr/share/applications/wine_xxx.desktops to a folder named wine and dir2sfs that folder. Then uninstall the wine.pet.
If you have some programs you always run under wine, install them as well before copying /root/.wine. Don't forget to copy any desktop files for them to your build folder.
Alternative-Tested:
I just created a wine.sfs by doing the following.
1. PaDs previously installed: http://murga-linux.com/puppy/viewtopic. ... 359#658359
2. Created a wine-2.16 folder: Right-Click empty space, select new directory, give it the name wine-2.16
3. Downloaded Version2013's wine-2.16 version 2.1 into wine-2.16 folder. Start here & follow links: http://murga-linux.com/puppy/viewtopic. ... 303#968303
Optional 3a. Remember that Version2013 does not include wine menus in his build. If you want wine programs to appear on your Start menu, also download wine_extras-v2.pet from here: https://version2013.yolasite.com/page1.php#wine-misc into the wine-2.16 folder.
4. Right-Click wine-2.16 folder and select "Combine to SFS". Combine to SFS is part of the PaDS application. A wine-2.16.SFS was created in /root.
5. Right-Click wine-2.16.SFS, select SFS-Load. SFS loaded.
6. Open terminal and type --without the quotes-- "wine winecfg". Config ran, installing gecko.
7. Open terminal and typed "wine winefile" -- wine's file-manager opened.
8. Used Linux file-manager to browse to portable-avidemux. Clicked avidemux.exe. Nothing happened.. Right-Clicked empty space and selected "open terminal here". Typed in terminal "wine avidemux.exe". Avidemux opened. Probably "exe" has to be added to "open with" routine.
mikesLr
New X-Slacko iteration released
Changes
* Bugfixes on power management and eee-pc mode
Download link: https://drive.google.com/open?id=0B2FRk ... WVpUmgxbVk
MD5 Checksum: 9d16efd8affffda79bf41b832cbbe4d9
Changes
* Bugfixes on power management and eee-pc mode
Download link: https://drive.google.com/open?id=0B2FRk ... WVpUmgxbVk
MD5 Checksum: 9d16efd8affffda79bf41b832cbbe4d9
Same:
"Dumping last lines of /tmp/bootinit.log...
etc
etc
Dumping last lines of kernel log...
etc
etc
etc
etc
*** puppy_slacko_4.2.sfs not found
***Error is too critical, dropping to console...
etc"
It doesn't 'drop to console' nothing at cursor is active.
...and
there was an HD present (Slacko) with a swap partition, but often there would not be an HD present. Sorry can't work with this configuration. r54 was last valid version.
"Dumping last lines of /tmp/bootinit.log...
etc
etc
Dumping last lines of kernel log...
etc
etc
etc
etc
*** puppy_slacko_4.2.sfs not found
***Error is too critical, dropping to console...
etc"
It doesn't 'drop to console' nothing at cursor is active.
...and
there was an HD present (Slacko) with a swap partition, but often there would not be an HD present. Sorry can't work with this configuration. r54 was last valid version.
Misunderstanding? The HD present has nothing to do with the liveCD I am trying to boot. Swap space, whether a file or partition, belonging to another, non-booted OS can normally be made available. There is no puppy_xslacko_4.2.sfs, ipso facto, I cannot 'replace' it. The another vmlinuz belongs to the Slacko installation and presumed not visible and or accessible?May I know the exact path where the puppy_xslacko_4.2.sfs file is saved? Can you try to replace the vmlinuz and the puppy_xslacko_4.2.sfs file on your Hard Drive and try to boot it up.
@Sage I test to boot X-Slacko Slim from live CD via Virtual Machine (Blank Hard Drive attached). It detects the puppy_xslacko_4.2.sfs, load to ram, and it works fine. That was weird that puppy_xslacko_4.2.sfs does not detect on your machine. Try to set these parameter before you boot puppy
Code: Select all
pmedia=cd
Doesn't work. GetTry to set these parameter before you boot puppy
Code:
pmedia=cd
Waiting for USB storage... {there isn't any}
Finding puppy main sfs file
Dumping....etc, etc.
/ # { can do 'ls' at this prompt, so some aspect of CLI is active}
All a bit of a disaster since r54, as you can see.
I have amassed a collection of several hundred Linux CDs. They all boot just fine, including your X-Slacko Silm, up to and including r54. Whatever you did after r54 isn't working.
New X-Slacko Slim iteration released
Changes:
* Added Nutyx package (*.cards.tar.xz) support via package conversion
* Some fixes on initrd
* Some fixes on remasterpup, shutdown scripts, edit-initramfs, and pburn
Download: https://drive.google.com/open?id=0B2FRk ... G5Na2o2dnM
MD5 Checksum: 0464161e9219d5bbca9db04385f07200
Changes:
* Added Nutyx package (*.cards.tar.xz) support via package conversion
* Some fixes on initrd
* Some fixes on remasterpup, shutdown scripts, edit-initramfs, and pburn
Download: https://drive.google.com/open?id=0B2FRk ... G5Na2o2dnM
MD5 Checksum: 0464161e9219d5bbca9db04385f07200