OP
VanillaCoffee
Active Member
Well that\s a bit stupid... so in other words Puppy is ruined or should be re-named the USB LIVE only Puppy or something. Oh well back to the old Bionic Puppy it is then.
Installing Bionic Puppy Linux to hard drive
- Thread starter VanillaCoffee
- Start date
My advice? Choose a distro that is MEANT to run from a full install, not one that isn't and then work your way around around to do so anyway. Even if you did manage to do a full puppy install it will negate ALL benefits AND most of the security from (any) puppy as intended.
Go for any other "light weight' distro like Devuan, Parrot <home, MS Linus, AntiX...........
One final tip on the Puppy thing: Configure your puppy as you like, layout, browser bookmarks and all other things. Use a Save File ON YOUR HARD DRIVE and from then on boot from your USB device , choose "load session in RAM" from the boot menu, unplug the USB device and use your puppy any way you want. Need to use your drive? You CAN if you order your puppy to do so and your experience will be like a full install.
wendy-lebaron
Well-Known Member
People want to be fed with applications and therefore 64-bit instead of 32-bit, and gigabytes instead of megabytes cannot be helped any longer.
Even worse there are the few who expect to be able to run 32-bit apps which will include a few hundred megabytes of 32-bit libraries. (Such as Arch Linux having a bunch of libraries that begin name with "lib32-".)
I have a Slackel installation on an external disk which is taking up half the space. But after it finishes starting up it usually takes up less than 400MB. It has been difficult to beat by anything else I have installed. Recently I installed Debian XFCE elsewhere, "Bullseye" without non-free firmware. That came with barely a hundred thousand files and 6.1GB or so. Also I have Bunsen Labs Beryllium which is about the same thing but wants almost 800MB after it finishes starting up.
So the memory requirements cannot be helped, and they will only increase in the future for the sake of comfort and security.
OP
VanillaCoffee
Active Member
Thanks everybody for your help. I managed to get Bionic Puppy installed to the internal SSD so I can grow my hair back now. This time I didn't follow any instructions I just sort of muddled my way through it not really sure what I was doing and I know I needed to check the boot flag which wasn't marked so I marked that. I did a system restart not expecting much to happen and I got something different this time and was asked if I want to do a full install so I proceeded and now I have Puppy Linux on my netbook.
This netbook only has a N455 single core Atom processor at 1.6GHz probably about as good as an intel Pentium 3 at 800MHz so the only light wight desktop environment that I know off is Puppy Linux and I had my heart set on making this little netbook into a Puppy Linux machine originally I'm chuffed I got Puppy finally installed. Its a shame about the new version.
This netbook only has a N455 single core Atom processor at 1.6GHz probably about as good as an intel Pentium 3 at 800MHz so the only light wight desktop environment that I know off is Puppy Linux and I had my heart set on making this little netbook into a Puppy Linux machine originally I'm chuffed I got Puppy finally installed. Its a shame about the new version.
Last edited:
OP
VanillaCoffee
Active Member
I liked it when there was a better selection of Linux Distros and I don't understand the need for small light weight distros that are 64 bit only they may as well scrap the light weight distros if they are just going to be 64 bit only. The whole point of light weight distros was to make older, less capable machines faster or run better. Its also rendering all those 32 bit machines useless for Linux. The days of reviving that old PC are going.
I have Bunsen Labs I like the basic look of it.
@VanillaCoffee :-
Sorry; I kinda lost track of where this was getting to. Had the decorators in fixing a water-damage insurance claim the last few days, so I haven't been paying attention like I normally would.
I just wanted to add that I, personally, haven't bothered with ANY of the multitude of various installers that have been crafted for Puppy.....not for several years. I run with the 'multiple sub-directories in a single partition' model (remember, OUR modified Grub4DOS bootloader has been re-configured to search TWO layers 'deep' in order to find a bootable kernel).
I perform a 'quick'n'dirty' install of Puppy every time. I have a dedicated partition - sda2 - just for my Pups & their associated save-files/folders, etc. I create a uniquely-named directory for a given Puppy, then simply mount its ISO and copy the contents across to the new directory.
Sda1 is a small, FAT32-formatted partition, necessary because despite running all Pups in 'Legacy' mode - no SecureBoot/FastBoot crap here, thank you very much! - this IS a modern machine with UEFI rather than BIOS.......and a FAT32 boot partition is a standard requirement for such, unfortunately. Ignore the 'standard' at your peril; the system hardware/firmware will throw a tantrum and refuse to 'play ball' if you do! This is where I install Grub4DOS to initially, then ever after all I do is a manual edit of 'menu.lst' to add another boot stanza.....I copy an existing one, then edit four words to change to the name of the new Puppy's directory. And that's ALL I do.
In your case, I suspect you don't have UEFI on that machine, but rather good old regular BIOS. In which case, you simply run the Grub4DOS installer, and point it at your primary partition.....it'll search the entire drive to find Puppy, so it doesn't matter where you put the Puppy directory. It'll still find it.
Glad to hear you got it sorted on your own, though. Kudos....and respect, my friend.
Mike.
Sorry; I kinda lost track of where this was getting to. Had the decorators in fixing a water-damage insurance claim the last few days, so I haven't been paying attention like I normally would.
I just wanted to add that I, personally, haven't bothered with ANY of the multitude of various installers that have been crafted for Puppy.....not for several years. I run with the 'multiple sub-directories in a single partition' model (remember, OUR modified Grub4DOS bootloader has been re-configured to search TWO layers 'deep' in order to find a bootable kernel).
I perform a 'quick'n'dirty' install of Puppy every time. I have a dedicated partition - sda2 - just for my Pups & their associated save-files/folders, etc. I create a uniquely-named directory for a given Puppy, then simply mount its ISO and copy the contents across to the new directory.
Sda1 is a small, FAT32-formatted partition, necessary because despite running all Pups in 'Legacy' mode - no SecureBoot/FastBoot crap here, thank you very much! - this IS a modern machine with UEFI rather than BIOS.......and a FAT32 boot partition is a standard requirement for such, unfortunately. Ignore the 'standard' at your peril; the system hardware/firmware will throw a tantrum and refuse to 'play ball' if you do! This is where I install Grub4DOS to initially, then ever after all I do is a manual edit of 'menu.lst' to add another boot stanza.....I copy an existing one, then edit four words to change to the name of the new Puppy's directory. And that's ALL I do.
In your case, I suspect you don't have UEFI on that machine, but rather good old regular BIOS. In which case, you simply run the Grub4DOS installer, and point it at your primary partition.....it'll search the entire drive to find Puppy, so it doesn't matter where you put the Puppy directory. It'll still find it.
Glad to hear you got it sorted on your own, though. Kudos....and respect, my friend.
Mike.
I am facing same issue well kinda same.
My spec are Pentium G2030 3.0GHz Ram ddr3 4GB. Remember the ram.
So this is my office PC which got old so i bought it and gave office a new PC as I run the office.
I bought the old PC home it ran window 7 or win 10. But the RAM was not working now.
So i got a RAM from my other old PC which ran puppy linux. I got the puppy linux PCs RAM and trying to install window 10 again ok my old office PC so i made a bootable USB window 10 runs the setup select the HDD (deleted partition made new again)where I want to install win 10 after installation is complete. The PC boots but i see this attached photo.
Wee is not a window command.
And I just installed windows 10 on this machine.
Why am i seeing this just because the RAM I used was installed in a machine with puppy linux installed?
Now How can i install win 10 on this office PC.?
Attachments
theLegionWithin
Well-Known Member
ram loses all data when it loses power - if you removed the ram sticks from one machine and put them in another machine, no data is "remembered" - it was all "lost" when you powered the first computer off.
is your goal to boot this up to windows10 only or have that and a distro of linux active as well?
Condobloke
Well-Known Member
What did you make the usb bootable to?....windows 10?
It is still trying to boot puppy....wee is a puppy command......so if you are using the same usb stick, you didnt make a successful, bootable win 10 usb
Got it. But why am I seeing this command line one in the previous post attached photo. The wee command line after I complete my window 10 installation process.
I also at times see the boot loan menu i have installed linux the the current PC before this. But how do I remove Linux from this machine completely and istalled windows 10?
theLegionWithin
Well-Known Member
first, back up anything you want from that computer.
after that:
- in the bios settings, change your boot order so that your first boot device is usb
- boot to the windows10 installer and then perform a clean install (aka format the drive, deleting all partitions) - there should be an option in there somewhere (maybe look to see if theres a video of it on youtube, etc).
- once the format is done, remove the usb disk and reboot
- this is a test to make sure the drive is wiped, you should receive an error that there is nothing to boot to
- now reinsert the usb disk and reboot, then reinstall windows10
Condobloke
Well-Known Member
I have used the same usb before and was successful to install windows 10. But only this machine is giving trouble i deleted and created new partition yet same i even complete the windows installation setup
Yes i did the same. I first deleted the hard disk deleted partition and created new n installed still same issue the windows setup in completed 100% but after i boot the screen shows the "wee command
"
Did you just delete a partition, or did you delete all partitions? You probably need to rebuild the entire partition table, and reformat the entire disk.
i want windows 10. But the installed RAM was previously used to run puppy linux on it. But i removed it hence it should run normally. I infact see the whole GRUB menu on blue screen I had used that RAM to run multiple linux distro separately
I deleted the whole partition first then created a new then it automatically created some 100mb of reserved partition and other 800 GB or so was new fresh partition and selected that partition to install windows 10. After completing the installation to 100% it did not boot into windows but got this command I will try again on Tuesday and check what I did wrong.
@prollet :-
A wee bit of background.
The "wee" error" derives from older versions of Puppy's Grub4DOS bootloader. It's from the bootloader's 'stage 1' which then tries to pass on the command to Grub4DOS's 'grldr' bootloader binary.
The older versions were 32-bit exclusively. The problem usually rears its head when the user tries to create an EXT4 filesystem with the older version of e2fsprogs that used to come with Puppy. The resulting EXT4 filesystem was 32-bit at heart, even though it's perfectly possible to install and run a 64-bit system on top of this.
IF, however, that EXT4 file-system was created from a more modern application, it will result in a 64-bit EXT4 filesystem. Ventoy will do this. Assuming that drive is then used to install a Puppy on, launched via Grub4DOS, it WILL fail.....because the older version of Grub4DOS was only able to 'read' the 32-bit variant of EXT4.
Nowadays, the Grub4DOS bootloader installer has been rebuilt into Grub2config. It works the same way, but instead incorporates the components from GRUB 2.12; hence, the issue never arises. However, it's still not identical to GRUB2 in behaviour; it doesn't use os-prober, for one thing. Puppy has its own way of detecting OSs on your drive that's worked successfully for us for many years.
Unfortunately, the 'wee' stuff has a tendency to embed itself into the drive's partition table.....and as @dos2unix has said, you need to clear/rebuild the partition table before you can use that drive for booting anything else.
It sounds complicated, I know.....but it's a 'legacy' of Puppy's former development history. As more & more people use Grub2config instead of the older Grub4DOS, the problem will eventually recede into the past....
Mike.
A wee bit of background.
The "wee" error" derives from older versions of Puppy's Grub4DOS bootloader. It's from the bootloader's 'stage 1' which then tries to pass on the command to Grub4DOS's 'grldr' bootloader binary.
The older versions were 32-bit exclusively. The problem usually rears its head when the user tries to create an EXT4 filesystem with the older version of e2fsprogs that used to come with Puppy. The resulting EXT4 filesystem was 32-bit at heart, even though it's perfectly possible to install and run a 64-bit system on top of this.
IF, however, that EXT4 file-system was created from a more modern application, it will result in a 64-bit EXT4 filesystem. Ventoy will do this. Assuming that drive is then used to install a Puppy on, launched via Grub4DOS, it WILL fail.....because the older version of Grub4DOS was only able to 'read' the 32-bit variant of EXT4.
Nowadays, the Grub4DOS bootloader installer has been rebuilt into Grub2config. It works the same way, but instead incorporates the components from GRUB 2.12; hence, the issue never arises. However, it's still not identical to GRUB2 in behaviour; it doesn't use os-prober, for one thing. Puppy has its own way of detecting OSs on your drive that's worked successfully for us for many years.
Unfortunately, the 'wee' stuff has a tendency to embed itself into the drive's partition table.....and as @dos2unix has said, you need to clear/rebuild the partition table before you can use that drive for booting anything else.
It sounds complicated, I know.....but it's a 'legacy' of Puppy's former development history. As more & more people use Grub2config instead of the older Grub4DOS, the problem will eventually recede into the past....
Mike.
Last edited:
theLegionWithin
Well-Known Member
to me it sounds like either another usb drive is connected somehow and its booting into grub, or you're not doing the deletion properly. try this:
- remove everything that's connected to the computer - cables, drives, etc. only attach a power cable to the computer, a video cable (for the monitor), a mouse, and a keyboard.
- go to the other computer & reformat that usb drive you've been using then re-create the win10 install disk on it (image with rufus/balena etcher or use microsoft's media creation tool software)
- on the computer that you want to install win10 to, get into the bios & factory reset it (reset to defaults) then reboot. then go back into the bios and set the boot order to boot to usb first
- now boot to the win10 installer
- in the installer, press Shift+F10 - this should open up a command window
- at the prompt, type in diskpart, then:
- list disk (shows the available disks)
- select disk X (where X is 0, 1, 2, 3, etc)
- clean (this will wipe everything)
- after using diskpart to wipe the drive, exit the installer and power the computer off
- open up the computer & disconnect all internal drives other than the one you want to install win10 on to
- power the computer back up and install win10 as you have been doing
if that fails then I would suggest throwing away the disk and buy a new ssd
