READ-ONLY Archive
https://oldforum.puppylinux.com/
64-bitnoryb009 wrote:: Thanks for trying it out, and I appreciate the bug report. Two things:
1) Are you running ..32-or-64-bit?
Well.. may have been a different (and much shorter! answer, if I hadn't gotten impatient and decidednoryb009 wrote::
2) Download and extract ...and overwrite the old lick-fltk.exe ...Run the file and try to install the boot loader. It should create two popups, one will be "Error installing loader!", what does the other say?
to create and install my own tahrpup.6.0.2>3.exe as per 1st post ...so I can't tell what it actually was BUT... I got some good feedback for you I think... it works fabulously and I think saved my butt 
Install lhg's groovy new spin PuppyBang via iso http://www.murga-linux.com/puppy/viewtopic.php?t=99969 b) (test) ran non-admin = popup = You must run as admin = good 
= not so good.. Decide not to Just say No (because I want it gone, right? No sweat, I can reinstall. 
) = not so good.. 
Sweat. Panic. 
Run LICK v.0.3. See Uninstall tab. Think it is to uninstall LICK. Click it anyway. Do I want to uninstall PuppyBang? 
Proceed. Do I want to uninstall grub4dos?:D Yes= (oh please Yes? 
Yes, please let this work and remove BOTH entries without calfing my W7 install/boot sector/anything? pretty please?!) LICK popup closes when done. Did it work?
Yes! Go back to 2.a) Test both. All good! 
(pun!) now that I am installing frugal to HD. (EDIT: Found, fixed, resolved.. on to the plan! 
) ) reliving that experience!!) Hopefully will create something useful in the process (if nothing else others may learn from my goofs. ) I hope something in my rambling is useful to you Hmm, the issue just went away? Interesting. I'll have to look at installing on systems which never had PLIC installed, then. I have to try out Win10 anyway, I'll see what happens then.charbaby66 wrote:2. a) followed your instructions re: LICK v.0.3. Ran as admin. Boot loader popup = No errors ?! well.. = good (?!)
Good. I'm assuming you switched by the UAC popup.Install lhg's groovy new spin PuppyBang via iso http://www.murga-linux.com/puppy/viewtopic.php?t=99969 b) (test) ran non-admin = popup = You must run as admin = good
Thanks for pointing this out, I'll have to rename the option ("Boot to LICK Loader", maybe?)3. Reboot. See 3 choices: Boot from Windows 7 or Boot to Puppy Linux or Boot to Puppy
Ya, this is another limitation of PLIC - it's awkward to manage the boot loader. Once the uninstaller runs, you don't want a run-this-to-remove-the-loader.exe hanging around, and I don't think people will download another file just to uninstall it. The "most correct" way right now to remove the loader would be to reinstall and reuninstall PLIC. But it's fixed in LICK, at least.4. Boot to 7, to uninstall Tahrpup6. Asked if to remove grub4dos? um..?.. Says if running other Linux versions say No. =
5. Reboot. See 3 choices: Boot from Windows 7 or Boot to Puppy Linux or Boot to Puppy
Interesting, I'll have to reconsider the design of the program. Maybe remove tabs and have everything visible? This shows the current design isn't working.6. Boot to 7, find no uninstaller in C:\<mypuppybangdir> like there was in C:\<mytahrdir>. =
That's the great thing about Lin'n'win, which PLIC/LICK is based on - it is very hard to ruin the windows install.Click it anyway. Do I want to uninstall PuppyBang?
I'm not sure why it worked. The way LICK looks at the loaders, it should only detect the LICK one, not the PLIC one. I'll have to look at this.LICK popup closes when done.
.
7. Reboot. See 1 choice: Boot from Windows 7
Great to hear you got it working in the end. Thank you so much for the post, I'll find the bugs so future users won't have to go through all this.8. Reboot. See 2 choices: Boot from Windows 7 or Boot to Puppy Linux = Oh yeah, baby, that's frickin' fabulous!!
LICK actually uses lickmenu.lst, it works exactly the same. It's pretty self-explanatory, and it's easy to see what needs to be changed if you have 2 different ISOs installed via LICK.I am rusty on what to add to LICK's menu.lst, (disk uuid?, correct partition #'s etc.) but used to copy/edit existing code for each new pup's entry. I am spoiled - using usb installs for so long I need to bone up
No I think when I did this from OP:noryb009 wrote:Hmm, the issue just went away? Interesting. I'll have to look at installing on systems which never had PLIC installed, then. I have to try out Win10 anyway, I'll see what happens then.
I had a PLIC installed right? Older LinNWin? Not sure, but your LNW splash screen was prettier I think.ADVANCED: Creating your own PLIC installer. To make your puppy into an .exe installer,..
I did not attempt using LICK again until after I uninstalled my PLIC via it's installer, so the issue may have uninstalled itself instead of just going away. Ugh, Win10 everything 8 should have had with less privacy added! Naw, just closed it. I already re-installed bang via LICK, I just wanted to see if I may have/could have installed non-admin is all. Thinkin' maybe that's how I broke my PLIC install, but can't think if it said needed admin or not..Good. I'm assuming you switched by the UAC popup.
Maybe, for continuity naming-wise for newbs who don't realise that new LNW window is part of LICK /installs the loader, but how many doofuses like me will end up with more than 2 boot loaders installed?Thanks for pointing this out, I'll have to rename the option ("Boot to LICK Loader", maybe?)
Yeah, that .exe unnerved me.Ya, this is another limitation of PLIC - it's awkward to manage the boot loader. Once the uninstaller runs, you don't want a run-this-to-remove-the-loader.exe hanging around, and I don't think people will download another file just to uninstall it. The "most correct" way right now to remove the loader would be to reinstall and reuninstall PLIC. But it's fixed in LICK, at least.
No, It's fine, I was in panic mode, and was unsure, a click was all it took (:idea: or just add the word Linux or something to the tab title if you mustInteresting, I'll have to reconsider the design of the program. Maybe remove tabs and have everything visible? This shows the current design isn't working.
)Good to know, I had a dual boot set up for at least a year on the craptop via grub4dos as per my last post that calfed the access to my ext2/3/4 partitioned pups after a power outage but still let me access my NTFS /W7 /Linux pups. That's partly why I went with usb not HD frugal installs.That's the great thing about Lin'n'win, which PLIC/LICK is based on - it is very hard to ruin the windows install.
I'm not sure why it worked. The way LICK looks at the loaders, it should only detect the LICK one, not the PLIC one. I'll have to look at this
Not as many as you seem to think, I'm sure! I'm a big LICK fan now.I'll find the bugs so future users won't have to go through all this.
Yeah, I caught that, but used to the other term, and I think the PLIC did use menu.lst .So I will read a bit more and figure out what to put in to run pups living on ext/2/3/4 with my NTFS kennel/W7. I was used to um.. hd0,0; chainloader and such being in there, but can't remember how I had it before.LICK actually uses lickmenu.lst, it works exactly the same. It's pretty self-explanatory, and it's easy to see what needs to be changed if you have 2 different ISOs installed via LICK.
Also some pups want/need the disk uuid now I think. (I know how to find mine just not where and when to put it.)You still faced an issue, which could appear in the future. I'll see if I can reproduce it.so the issue may have uninstalled itself instead of just going away
I just finished trying out Win10 (luckily it's the same bootloader as 8, so just a few lines of extra code needed), that's a good way to describe it. I like it, but not enough to make me change back from Linux, though.Win10 everything 8 should have had with less privacy added!
It uninstalled something that shouldn't have been installed. While it was good in this case, it's still a bug.I think it's a feature not a bug!
I just finished trying out Win10 (luckily it's the same bootloader as 8, so just a few lines of extra code needed), that's a good way to describe it. I like it, but not enough to make me change back from Linux, though.
LOL I should hope not! You know which Win I liked best??? 98SE!! still have it somewhere Guess the ol' gal still has got it goin' on!! ) now I can link out wine, fiddle with NF, un/squash me an .sfs, & do some remastering just a lil bit easier with 2 emergency Pups on sda1 <bark bark> The plan continues... hey buddynoryb009 wrote:LICK v0.3.1 is released.
quick ?? for you. Gonna mess around with lappy during bus ride. Have a usb case & lappy hd in it, with older series 5 pups on it, used to use something not LICK to boot it. It may have XP on it. May not have wifi all the way, but enough to see your reply once I get to the depot I'm out the door as soon as I post this.Code: Select all
title USB HDD
find --set-root --ignore-floppies /a/file/on/HDD
chainloader ()+1
bootnoryb009 wrote:Install Puppy Linux on Windows
Most people who come here are probably looking for this link, hosting a Windows installer for the most recent official Puppy Linux, as well as a few derivatives. There is also a mirror, provided by archive.org.
Windows installers for a few Puppy Linux derivatives:
Italian Puppy: Multiple versions
Sagelive: 511
Quickset Wary: 511
Japanese Precise: 571 | 550 | 420
Puppy Linux Turbopup Xtreme: 420
Puppy Linux 525 | 520
Project info
Puppy Linux Installer Creator (PLIC) is a set of NSIS scripts that can create an EXE that can install Puppy Linux onto a Windows system without touching the MBR. It follows the Lin'N'Win method.
PLIC installers work on all versions of Windows, from 95 to 8, except ME. On a Windows 8 system, ensure fast boot is disabled, secure boot is disabled and the UEFI set to Legacy (BIOS) mode.
PLIC installers can install one version of Puppy Linux each. Each installer includes a simple uninstaller. You can have any number of PLIC installers installed.
ADVANCED: Creating your own PLIC installer
To make your puppy into an .exe installer, you must use Windows or wine. Install NSIS onto it (select all the plugins when asked). Then, unzip the PLIC scripts and follow the instructions in README.txt.
Big thanks to shinobar and mikeb for windows 7 help, seeker for creating the original windows installer, and Brian Grainger for the Lin'N'Win guide.
View the project on Github