Page 1 of 7
BusterDog + build system (no-systemd)
Posted: Mon Jul 13, 2020 4:07 pm
by fredx181
*** BusterDog + build system *** (updated 2020-09-07, added UEFI support for 64-bit version, thanks @jamesbond !)
See Here for a Buster-Live build system. edit: updated 2023-06-04 see info here: viewtopic.php?p=90875#p90875
Based on the Debian 'Buster' branch but without systemd.
It's using special method (taken from AntiX) to avoid systemd by replacing systemd with 'elogind'.
(and some more, e.g. libsystemd replaced by libelogind), more background info Here
EDIT: For how to boot BusterDog with systemd, see here: https://puppylinux.rockedge.org/viewtop ... p=208#p208
Download: 32 and 64 bit ISO's (updated 2020-09-07), see Here, boot options (grub4dos): Examples-boot-codes
DEVX and Firmware squashfs modules: Here
Custom repository: 32-bit 64-bit
Login details:
root with password root
puppy with password puppy
Specifications:
Built from scratch by using debootstrap and remastered afterwards.
Kernel: 4.19.0-9 for 32-bit version (the kernel is separate module) for 64-bit version, kernel 4.19.0-10
Choice of Boot Methods: porteus-boot and live-boot v3 (see for options: Examples-boot-codes)
(EDIT: See post #4 for how to boot with older kernel 3.16 if possibly your hardware is too old for booting v4.19)
Default WM - OpenBox, with Desktop choices (run ‘Desktop Manager’ to choose):
- Tint2 panels
- PcmanFM providing the Desktop and lxpanel
- Tint2 bottom panel and rox-pinboard providing the Desktop
Option to switch to JWM window-manager
Default File Manager - PcmanFM with option to use rox.
Default Internet Browser - Palemoon.
Thanks very much to everyone who has been involved with DebianDog, specially Toni (saintless), William (mcewanw), Terry (sunburnt), dancytron, belham2, rcrsn51, wiak, jd7654, backi, AndresC2, peebee and all who helped by giving feedback on the DebianDog threads.
Screenshots:
Openbox tint2 panels:
Pcmanfm + Lxpanel:
Re: BusterDog + build system (no-systemd)
Posted: Mon Jul 13, 2020 4:07 pm
by fredx181
*** Changes and Fixes ***
For BusterDog-openbox_jwm-2020-06-29 version:
- Kernel upgraded to v4.19.0-9
- Added the +EXIT option for on the boot commandline, e.g. changes=+EXIT:/BusterDog/live (save on demand or at shutdown, temporary changes NOT in RAM)
(see more info and example: Examples-boot-codes.txt)
- Added some more applications, e.g. Pmusic, pequalizer, and more
- Added 'Xlunch' to the Desktop choices in Desktop Manager
- Palemoon upgraded to v28.10.0
- Upgraded all packages to newest versions
-----------------------------------------------------------------------
For BusterDog-openbox_jwm-2019-12-29 version:
- Changed timezone to default UTC (forgot earlier)
EDIT 2019-12-30, re-uploaded 64-bit ISO including small fix
-----------------------------------------------------------------------
For BusterDog-openbox_jwm-2019-12-28 version:
- Fixed the annoying delay of the openbox menu display.
- Some small changes to menu(s)
- Upgraded Palemoon and other software (apt upgrade)
- Added some more applications
-----------------------------------------------------------------------
For BusterDog-openbox_jwm-2020-09-07 UEFI version (64-bit):
- Added UEFI support
- Kernel upgraded to v4.19.0-10
- Upgrade all packages (apt upgrade)
Re: BusterDog + build system (no-systemd)
Posted: Mon Jul 13, 2020 4:07 pm
by fredx181
*** Debian Buster and avoiding systemd **
Standard Debian Buster has systemd enabled, from the beginning I've been searching for a way to avoid systemd and used Devuan as a base: DevuanDog 'Beowulf' [DISCONTINUED]
Now, DevuanDog is discontinued because I found a self-supporting way (not being dependent on Devuan) to avoid systemd:
BusterDog has similar method as AntiX by replacing systemd with 'elogind'.
This way BusterDog runs with the old initscripts method (sysvinit)
Fred
Re: BusterDog + build system (no-systemd)
Posted: Mon Jul 13, 2020 4:08 pm
by fredx181
How to install systemd on BusterDog:
For those who prefer booting with systemd, here's how (a bit of a workaround)
First make sure to Exit X ! Menu > Logout > Exit X
Then from the console type ("apt update" may not be needed if you recently updated the package lists):
Code: Select all
apt update
apt install udev systemd-sysv libpam-systemd
Reboot with changes saved and systemd will be the init system.
(automatic login doesn't work then, btw).
Note: after doing above and booting with systemd, there's no way back to switch to elogind again (at least that I know of)
Fred
Re: BusterDog + build system (no-systemd)
Posted: Sun Jul 26, 2020 10:41 am
by +Me
G'day Fred, Thanx 4 this 64 Bit BusterDog.
I've just Discovered an ideal Free Open Source Note taking & To Do List App Joplin that's X Platform which Suits my Requirements, I've Successfully installed it on Linux Lite ( a Kiwi XFCE Ubuntu Flavor ), MacOS, M$ Virus Magnet WinDoze & Android. Yes I Really Do use All those OSes
https://joplinapp.org/
But when I Try 2 install it on me Favorite Flavor of Linux it Complains about being root... I did insert the option of allow-root B4 the wget script, But I couldn't get it 2 work 4 me, I don't know wot I'm doing wRong... Can yoU Please Help me? Thanx ;-)K
Ps. Stay Healthy & Safe & Away from that Contagious ToyMota Virus! ( Sorry Mate, But I'm Still Haunted by the Rusty ToyMota Coronas in 70s & 80s when I waz a PanelBeater over 1/2 a Lifetime ago ) !!!
Re: BusterDog + build system (no-systemd)
Posted: Mon Jul 27, 2020 2:41 am
by dancytron
Try the "run-as-user" program. It will run just that program as a different, non-root user.
In a console window type "run-as-user NameOfProgram".
If you don't know the name, open it's .desktop file in leafpad and see. They are in /usr/shared/applications.
You can then write a script or edit the .desktop file to do it all the time.
Re: BusterDog + build system (no-systemd)
Posted: Mon Jul 27, 2020 6:20 am
by +Me
Thanx Dancytron 4 your reply, Thanx 2 yoU I've maid progress, but I'm not quite there... it's saying NOT DONE, unknown desktop 'openbox'.
Wot Now? Please & Thanx 4 your Help...
;-)K
Re: BusterDog + build system (no-systemd)
Posted: Mon Jul 27, 2020 10:05 am
by +Me
I've also since found a Joplin AppImage that wood be my preference / ideal if I could only get it 2 run ( of course I've made it executable )
I'm also Trying 2 Run a FreeTube AppImage & having the same Challenges & found a FreeTube.deb that said it installed But won't Run... Please Help!
Re: BusterDog + build system (no-systemd)
Posted: Mon Jul 27, 2020 11:06 am
by fredx181
Running the appimage with the --no-sandbox option works for me, e.g:
Code: Select all
/root/Downloads/Joplin-1.0.227.AppImage --no-sandbox
EDIT: I downloaded the appimage by clicking on the "Get on Linux" button and then made it executable.
https://github.com/laurent22/joplin/rel ... 7.AppImage
Fred
Re: BusterDog + build system (no-systemd)
Posted: Mon Jul 27, 2020 3:25 pm
by dancytron
+Me wrote: ↑Mon Jul 27, 2020 10:05 am
I've also since found a Joplin AppImage that wood be my preference / ideal if I could only get it 2 run ( of course I've made it executable )
I'm also Trying 2 Run a FreeTube AppImage & having the same Challenges & found a FreeTube.deb that said it installed But won't Run... Please Help!
Try putting the appimage file into /home/puppy. Right click--properties and see who the owner of the app image is. Try changing the owner and group to puppy or visa versa.
Fred's way is to get it to run as root by bypassing the security thing that is stopping you. My way is trying to run it as the regular user "puppy".
Re: BusterDog + build system (no-systemd)
Posted: Mon Jul 27, 2020 4:04 pm
by +Me
Yay Thanx Fred, Both AppImages Work!!! ( altho I think there were a Lot of Warnings & it Seems that I Need 2 Keep the Terminal Windows Open Otherwize their Respective AppImage iz Killed! )
Next I'll Try Dancytrons method...
Thank yoU Both, I couldn't have done it without your Help!
;-)K
Re: BusterDog + build system (no-systemd)
Posted: Thu Jul 30, 2020 5:17 am
by +Me
G'day Guys, No Luck getting Dancytrons Method 2 work.
I'd like 2 Clean Up the Starting of AppImages that give 60 - 70 Gtk WARNINGS about Error Parsing Themes in the Terminal Window & then the Cursor doesn't offer a # or $ so it's a Crippled Terminal that I can't use! How can I Fix this? Please
ideally I'd like 2 Launch these AppImages by Clicking on the File or Better still the icon, Launching it from the Panel or otherwize the desktop, But I don't know How 2 do this, eSpecially since they Need the --no-sandbox option
Please Help...
;-)K
Re: BusterDog + build system (no-systemd)
Posted: Fri Jul 31, 2020 1:52 am
by +Me
Please Help, I couldn't find CUPS or Printer Setup... then Discovered it wasn't installed, so then did so via Synaptic, But it's still not showing in the Menus, I've Tried calling it from the Terminal, But it just Returns bash: cups: command not found...
Sorry I don't mean 2 be a Pest ;-(
;-)K
Re: BusterDog + build system (no-systemd)
Posted: Fri Jul 31, 2020 3:31 am
by dancytron
One of the differences between Debian Dog and Puppy is that a lot of stuff like CUPs that comes in Puppy by default isn't in Debian dog.
Cups has a web interface to set it up.
https://wiki.debian.org/CUPSPrintQueues ... binterface
http://localhost:631
Re: BusterDog + build system (no-systemd)
Posted: Fri Jul 31, 2020 3:33 am
by dancytron
+Me wrote: ↑Thu Jul 30, 2020 5:17 am
G'day Guys, No Luck getting Dancytrons Method 2 work.
I'd like 2 Clean Up the Starting of AppImages that give 60 - 70 Gtk WARNINGS about Error Parsing Themes in the Terminal Window & then the Cursor doesn't offer a # or $ so it's a Crippled Terminal that I can't use! How can I Fix this? Please
ideally I'd like 2 Launch these AppImages by Clicking on the File or Better still the icon, Launching it from the Panel or otherwize the desktop, But I don't know How 2 do this, eSpecially since they Need the --no-sandbox option
Please Help...
;-)K
Don't worry about the warnings. Chrome/Chromium based apps are noisy like that.
Probably the easiest way is to write a little script.
Move the appimage to /usr/local/bin and then take the attached script, remove the .gz, mark it executable (Right click--Properties--Permissions--Execute-Anyone), and then click on the script to run Joplin.
Re: BusterDog + build system (no-systemd)
Posted: Fri Jul 31, 2020 9:11 am
by fredx181
Or create a .desktop launcher by pasting below in a text file, change Exec= path below to what's yours, save e.g. as joplin.desktop in /usr/share/applications, save attached joplin.png in /usr/share/pixmaps.
Then you can run from Menu (may need some time to apply)
Code: Select all
[Desktop Entry]
Version=1.0
Name=Joplin
Comment=Note taking and to-do application
GenericName=Joplin
Exec=/root/Downloads/Joplin-1.0.227.AppImage --no-sandbox
Terminal=false
Type=Application
Icon=joplin
Categories=Office
Fred
Re: BusterDog + build system (no-systemd)
Posted: Fri Jul 31, 2020 9:15 am
by +Me
Thanx again Dancytron 4 your Support.
Your Script Worked w/ Joplin so I Edited it 2 Work w/ FreeTube AppImage & Stellarium AppImages. ideally I Wish I could Launch them from the Panel / Task Bar or Desktop.
But More importantly getting me Old MonoKrome HP LaserJet P1505 w/ a near new Toner Cartridge 2 work iz the Priority. This iz a USB Printer & doesn't have Network Connectivity, so isn't detected by the Web interface.
Please Help Thanx!
;-)K
Re: BusterDog + build system (no-systemd)
Posted: Fri Jul 31, 2020 10:36 am
by +Me
Thanx Fred, that Worked, Joplin went into the Office Menu which iz OK.
I'll Try & do likewize w/ FreeTube & Stellarium AppImages.
I Wunder if yoU might Consider including these Very Useful Apps in Future?
Also I Wish there waz a More Flexible Printer Setup that doesn't require Eth0 or Wireless
Thanx again 4 your Help
;-)K
Re: BusterDog + build system (no-systemd)
Posted: Fri Aug 14, 2020 8:15 pm
by stemsee
Im trying to build on fatdog64. Keeps throwing up this error.
- mklive64.png (110.06 KiB) Viewed 2991 times
any ideas?
I didnt find elogind in the gui lists either!
stemsee
Re: BusterDog + build system (no-systemd)
Posted: Fri Aug 14, 2020 10:42 pm
by fredx181
Hi stemsee, what exactly did you use / do ?
I've just tested building on fatdog running appimage "mklive-buster64" (needed to install perl from gslapt first) and it went well.
Running the bare script "mklive-buster" should work also, but I think it needs dpkg installed from gslapt (the appimage has it included).
I didnt find elogind in the gui lists either!
Install is done in the script, as it's a required package.
Fred
Re: BusterDog + build system (no-systemd)
Posted: Sat Aug 15, 2020 6:54 am
by stemsee
I tried again having loaded the devx for perl. Installed dpkg. Ran mklive with -gui selected defaults for first selection and let it run. Changes passwords at prompts, selected keyboard. Same result! Tried the full Chrome option....failed also!
stemsee
Re: BusterDog + build system (no-systemd)
Posted: Sat Aug 15, 2020 8:33 am
by fredx181
stemsee wrote: ↑Sat Aug 15, 2020 6:54 am
I tried again having loaded the devx for perl. Installed dpkg. Ran mklive with -gui selected defaults for first selection and let it run. Changes passwords at prompts, selected keyboard. Same result! Tried the full Chrome option....failed also!
stemsee
Did you run the appimage or the script ? I'd recommend the appimage, from
https://debiandog.github.io/MakeLive/Re ... erdog.html:
Rather than just one script it’s now packed as appimage, reason is that this way it works ‘out of the box’ on most OS’s including modern puppies. The appimage has included e.g. yad, debootstrap, dpkg, xorriso (for creating ISO), so nothing extra is required to install. Tested on Tahrpup, Xenialpup, Dpup-Stretch, DebianDog, Fatdog (but on the latter I needed to install ‘perl’ first from gslapt).
Anyway, I tested now also running the script "mklive-buster", after installing perl and dpkg, and it went fine, except for creating ISO, because xorriso wasn't installed (on Fatdog 810).
So.... I have no idea why you got the errors
Fred
Re: BusterDog + build system (no-systemd)
Posted: Sat Aug 15, 2020 11:53 am
by johnevans
+Me wrote: ↑Sun Jul 26, 2020 10:41 am
But when I Try 2 install it on me Favorite Flavor of Linux it Complains about being root... I did insert the option of allow-root B4 the wget script, But I couldn't get it 2 work 4 me, I don't know wot I'm doing wRong... Can yoU Please Help me? Thanx ;-)K
I had a similar problem when I tried to install WhatsApp on my Linux, so I searched the net and found this
FM WhatsApp modified app of WhatsApp. After installing this app, I found out. Come on, this is an unofficial app that was developed by a Spanish developer, so I immediately deleted this app from my Linux, but I'm still looking for a solution.
Re: BusterDog + build system (no-systemd)
Posted: Sat Aug 15, 2020 8:16 pm
by stemsee
tried both. Exactly that one linked.
Re: BusterDog + build system (no-systemd)
Posted: Wed Aug 19, 2020 6:49 pm
by wanderer
hi fredx
am using your BusterDog now
absolutely fantastic
thanks so much for all your creations
wanderer
Re: BusterDog + build system (no-systemd)
Posted: Thu Aug 20, 2020 6:57 am
by +Me
G'day Fred, I'm eMbarrassed 2 ask where iz the Recommended Location of Home in this BusterDog?
in the PCManFM File Manager when I Clic' on the Home Folder in the Left hand panel it Opens /root in the Rite hand pane w/ all of my Personal Files az I'd eXpect Plus Plenty of Hidden System Files I Assume because they're preceded by a " . " ( ie. period ). But if I Clic' on the FileSystem Root Directory in the Left hand pane it Opens " / " ( ie. Actual Root ) But the Confusion doesn't eNd there, because then if I Clic' on the Home Directory in the Rite hand pane it Opens 2 the /puppy Directory just by itself, Within which again haz more Hidden Files & Directories ( Actually less in Total than the Other Home Location ) & Nun of my Files! I'm Lost & Confused!
The Reason I'm asking iz because I'm Struggling 2 Understand where the Space haz gone in my 240 GB SSD, Frugal install Sharing the SSD w/ M$ Virus Magnet WinDoze. I'm Vigilantly Manually Moved DownLoads & Big Files from within the saveme.dat or changes.dat File & Frequently getting Nagged about being down 2 just 30 Mb in the Root FileSystem ( or similar Message ). Of Course I'm Regularly ReSizing the Save File, it's Currently 6 GB But of Course the Other Rationale 4 Moving those Files Out of the changes.dat File iz in case I have 2 access them from the Evil M$ Virus Magnet WinDoze.
Yet it's a Constant Battle! I Welcome All Suggestions & a Better Understanding about the Recommended Home Location & whY, Thanx!
;-)K
Re: BusterDog + build system (no-systemd)
Posted: Thu Aug 20, 2020 1:55 pm
by fredx181
+Me wrote:G'day Fred, I'm eMbarrassed 2 ask where iz the Recommended Location of Home in this BusterDog?
in the PCManFM File Manager when I Clic' on the Home Folder in the Left hand panel it Opens /root in the Rite hand pane w/ all of my Personal Files az I'd eXpect Plus Plenty of Hidden System Files I Assume because they're preceded by a " . " ( ie. period ). But if I Clic' on the FileSystem Root Directory in the Left hand pane it Opens " / " ( ie. Actual Root ) But the Confusion doesn't eNd there, because then if I Clic' on the Home Directory in the Rite hand pane it Opens 2 the /puppy Directory just by itself, Within which again haz more Hidden Files & Directories ( Actually less in Total than the Other Home Location ) & Nun of my Files! I'm Lost & Confused!
Understandable that it's confusing, I'll try to explain.
You are logged in as root (default, superuser), so the Home folder on the left pane opens /root
You can also login as unprivileged user, Exit X > type on console
login, type
puppy , type password of puppy:
puppy
(user puppy is existing user in Busterdog, but you can create other user with your own name and login as that user)
So suppose you are logged in as unprivileged user, then (in case of puppy), clicking on Home in pcmanfm will open /home/puppy
Logged in as other user you created, say "max" will also open in /home, e.g. /home/max
The Reason I'm asking iz because I'm Struggling 2 Understand where the Space haz gone in my 240 GB SSD, Frugal install Sharing the SSD w/ M$ Virus Magnet WinDoze. I'm Vigilantly Manually Moved DownLoads & Big Files from within the saveme.dat or changes.dat File & Frequently getting Nagged about being down 2 just 30 Mb in the Root FileSystem ( or similar Message ). Of Course I'm Regularly ReSizing the Save File, it's Currently 6 GB But of Course the Other Rationale 4 Moving those Files Out of the changes.dat File iz in case I have 2 access them from the Evil M$ Virus Magnet WinDoze.
I'm not sure to understand what you mean exactly and what's your question. Anyway, I think you mean the "home"
partition, I have no idea why the nagging about being down 2 just 30 Mb in the Root FileSystem, is the 6GB savefile almost full ?
Isn't it the sda1 partition that is the windows partition on pcmanfm left pane ? Not? then try /mnt/home (should open the frugal install partition) or /live/image.
EDIT: maybe I see what you mean now, yes, find the windows partition (in /mnt/home but could be also /mnt/live/mnt/sda1) and cut and paste the files you want to move (that are are e.g. in /root/Downloads, or anywhere) into it.
Hope this helps.
Fred
Re: BusterDog + build system (no-systemd)
Posted: Thu Aug 20, 2020 11:15 pm
by +Me
Thanx Fred 4 your Reply, I'm Not sure that I'm understanding your eXplanation or if We're on the same page?
But after Yet More Perseverance / Persistence I've Discovered sumthing that I'm Suspicious about ( But I'm Really Not sure if it's correct? )
When I Clic' on sda2 in the Left hand pane of PCManFM it Opens to /mnt/live/mnt/sda2 rather than /mnt/sda2 az I wood have eXpected, because my changes.dat File iz Located @ /mnt/live/mnt/sda2/live/changes.dat ( iz this Normal? Because it seems like Too Much Duplication of Layers or Levels ie. /mnt & /live being Duplicated, I think that's Complicated & Confusing me ! ).
Because When I Attempt 2 Resize my Save File it Complains that it's Mounted & Can't! ( Previously in Puppy it'll Resize the Save File @ Reboot )
& then Ultimately that Suspicious issue haz a Beering on my menu.lst changes.dat Location address File, But I Really want 2 have Peace of Mind that those Layers aRe Correct 1st B4 I Edit my menu.lst File.
Thanx 4 your Support
;-)K
Re: BusterDog + build system (no-systemd)
Posted: Fri Aug 21, 2020 4:01 am
by +Me
Stop Press ( Talking 2 Myself, Because I couldn't Resist the Temptation of Editing the menu.lst File, But Not B4 Creating a New Save.dat File & Noticing that it's Default Location )( inside Directory Nun ), I think iz /mnt/sda2/live? from Memory ( Because Now I can't redo it, Because in Creating a New Save File I had 2 ReDo my AppImages & Scripts etc & in doing so I've Broken Sumthing that Now the Menu Button doesn't work & just presents an Openbox window saying invalid output from pipe-menu "obox-menu ddog-applications.menu" that I don't understand, let alone How 2 Fix it ), Even tho Clearly it waz All my Fawlt! Furthermore Conducting an iNet Search Drew a Blank! So I'm Stuck Again & @ the Mercy of your Help!
Edit it just occurred 2 me 2 minimize All the windows & Rite Clic' on the Desktop 2 get the Menu 2 ReCreate the Save File, eXcept that your Special DDog Menu haz Run Away! ;-(
Other than that on the issue of the .dat File, I think I maybe making progress, But I'd Still Appreciate your Confirmation of the Result in that Now the Path 2 my ******.dat File in my menu.lst iz /mnt/sda2/live/saveme.dat Does that Look Rite? The Strange thing 2 me iz that when I go 2 that Location, there's Nuthing there, Not Even me ******.dat File. So I'm Fuzzy / Blurry, Not Krystal Clear az I'd Prefer 2 be & if I'm on the Rite Track...
Thanx!
;-)K
Re: BusterDog + build system (no-systemd)
Posted: Fri Aug 21, 2020 12:26 pm
by fredx181
+Me wrote:When I Clic' on sda2 in the Left hand pane of PCManFM it Opens to /mnt/live/mnt/sda2 rather than /mnt/sda2 az I wood have eXpected, because my changes.dat File iz Located @ /mnt/live/mnt/sda2/live/changes.dat ( iz this Normal? Because it seems like Too Much Duplication of Layers or Levels ie. /mnt & /live being Duplicated, I think that's Complicated & Confusing me ! ).
Confusing, yes I admit, but there's nothing to worry about, I've seen that too that in some cases (depends on how you boot) the mountpoint has become /mnt/live/mnt/sda2, even when specifying /mnt/sda2 in menu.lst, as long as the savefile is loaded, it's ok.
So yes, if the path when running the system is /mnt/live/mnt/sda2/live/changes.dat it's normal. But... Do NOT specify it in menu.lst that way.
Because When I Attempt 2 Resize my Save File it Complains that it's Mounted & Can't! ( Previously in Puppy it'll Resize the Save File @ Reboot )
When the savefile is loaded, it cannot be resized properly (anyway I wouldn't know how), so you need to do it booting without save i.e. remove changes=.... from kernel commandline (or boot with another save) or boot another distro to do the resizing.
Stop Press ( Talking 2 Myself, Because I couldn't Resist the Temptation of Editing the menu.lst File, But Not B4 Creating a New Save.dat File & Noticing that it's Default Location )( inside Directory Nun ), I think iz /mnt/sda2/live? from Memory ( Because Now I can't redo it, Because in Creating a New Save File I had 2 ReDo my AppImages & Scripts etc & in doing so I've Broken Sumthing that Now the Menu Button doesn't work & just presents an Openbox window saying invalid output from pipe-menu "obox-menu ddog-applications.menu" that I don't understand, let alone How 2 Fix it ), Even tho Clearly it waz All my Fawlt! Furthermore Conducting an iNet Search Drew a Blank! So I'm Stuck Again & @ the Mercy of your Help!
Sorry, I have no idea what happened exactly and how to fix, except trying again to create new savefile and booting with it.
But I'd Still Appreciate your Confirmation of the Result in that Now the Path 2 my ******.dat File in my menu.lst iz /mnt/sda2/live/saveme.dat Does that Look Rite?
Yes, is right, but just a tip, if there exist only one /live/saveme.dat in all your partitions, it's enough to specify only that, then instead of /mnt/sda2/live/saveme.dat, just changes=/live/saveme.dat, it will be found because at boot it's searching all partitions for /live/saveme.dat
And be sure that there is no other "live" folder, e.g. from other Dog distro, on any other partition, it may lead to conflict.
Fred