Page 12 of 30
No idea how to make my own exe
Posted: Sat 23 Mar 2013, 14:52
by danneauxs
OK, I admit the directions were a bit to essoteric for me. Prob if I had half an idea what I was doing they would but clueless so I did my own cludge to load the puppy verision I wanted.
I add puppies to my linux machine simply by making a directory, copying the proper files into it and adding an entry to my grub.
Basically I did the same thing on my windows machine thanks to the windows installer. I simply installed one of the pre-compiled installers which did all the work (grub4dos) for me. I make a folder, copy the puppy files from the ISO I'm testing that day and add an entry to the menu.lst. Done and easy.
I'll prob ask for help making my own exe in a while so I can take my favorite pup to install on friends windows pc's.
Thanks
Danneauxs
Windows 8 support
Posted: Sat 11 May 2013, 05:02
by shinobar
Hello.
How about supporting Windows 8?
I guess we need to use the 'compatible mode' on Windows 8.
Posted: Sat 11 May 2013, 14:54
by noryb009
I tried to add windows 8 support before, but there were a lot of glitches when running it in virtual box, so I decided to leave it. I tried it again today, and it seems to be working. I've made the changes but I've only tested it on 32-bit, without UEFI or secure boot. I'm pretty sure it will work fine with 64-bit, but I'm not sure about secure boot when it is enabled.
If someone can test it on 64-bit or with UEFI/secure boot, that would be appreciated! I've compiled an installer for
pUPnGO (~7MB), or you can make your own installer from the code
here.
Re: Windows 8 support
Posted: Mon 13 May 2013, 04:28
by shinobar
Thanks noryb009 for the quick response on the Windows 8 support.
Unfortunately I have no Windows 8 yet.
But I tried merging your code with PIC-NLS with Japanese.nsh to support Windows 8.
One more thing, i add *.4fs at Uninstall in the main.nsi.
http://shino.pos.to/party/bridge.cgi?puppy/test/
Posted: Mon 13 May 2013, 19:19
by noryb009
Hopefully somebody who has windows 8 will find it and try it out.
One more thing, i add *.4fs at Uninstall in the main.nsi.
Thanks, I've added this.
EDIT:
But I tried merging your code with PIC-NLS with Japanese.nsh to support Windows 8.
I've added NLS support to the main code base, but have not yet added any translations. If you want to not have to merge future code to your fork and benefit the main code at the same time, you can make a translation file
here, then send it to me.
Russian translation
Posted: Thu 16 May 2013, 19:00
by rodin.s
I have made Russian translation.
Posted: Thu 16 May 2013, 20:40
by noryb009
Thank you, rodin.s!
Windows 8 and Japanese support
Posted: Thu 16 May 2013, 23:07
by shinobar
shinobar wrote:Thanks noryb009 for the quick response on the Windows 8 support.
Unfortunately I have no Windows 8 yet.
But I tried merging your code with PIC-NLS with Japanese.nsh to support Windows 8.
One more thing, i add *.4fs at Uninstall in the main.nsi.
http://shino.pos.to/party/bridge.cgi?puppy/test/
There is the Japanese translation: PIC-NLS-win8-2013-05-12.tar.gz
Made Puppy-Linux-549JP03.exe (test release).
http://shino.pos.to/party/bridge.cgi?pu ... cise/test/
I tested t on the Windows 8 enterprise both 32bit/64bit and works OK.
Posted: Sat 18 May 2013, 19:51
by noryb009
It's great that it works on 64-bit! Do you know if the computers you tried it on had UEFI or secure boot enabled?
UEFI boot
Posted: Sun 19 May 2013, 07:39
by shinobar
noryb009 wrote:Do you know if the computers you tried it on had UEFI or secure boot enabled?
I tried on the VmPlayer with 'firmware="efi'. The installer maybe worked correctly (see the bcd entries below),
But it fails to boot up puppy.
I suppose the grub4dos is not compatible with UEFI.
Posted: Sun 19 May 2013, 16:25
by noryb009
Thanks for testing UEFI. I'll look into ways we can get it to work.
Posted: Wed 22 May 2013, 00:51
by noryb009
Precise Puppy Linux 560 has been uploaded, see the link in the first post.
It includes Windows 8 support when BIOS is enabled (not UEFI yet) and secure boot off.
I did not include the Russian translation, as I still need to do a bit more testing with it (I was going to include it, then found a mistake in the code, so I skipped it for now). It will probably be enabled in the next build.
Posted: Thu 23 May 2013, 00:10
by don570
All Macintosh computers using Intel chips use UEFI and many users
run Windows on their mac computer. So if you can get the installer to
work on a Mac computer running windows that would be quite an
achievement.
________________________________________
Posted: Thu 23 May 2013, 02:23
by noryb009
Thanks for the suggestion, but I don't know if I could get that to work. If it works once UEFI support for windows is added, great. If it doesn't, I won't spend any time on it, as I don't have access to a mac.
Posted: Thu 23 May 2013, 02:56
by 01micko
Sorry for OT noryb009, but to address don570's concern with mac computers:
My wife has a recent macbook air, purchased at the beginning of this year. I stumbled upon someone booting Fedora off a usb stick on their macbook air
here. According to that articele, it boots no problem from a FAT usb stick holding down the "Option" key.
I decided to try this with a stick I had lying around that had PHATSlacko on it on and f2fs drive, using syslinux to boot from a FAT partition. It failed. But, I had another stick lying around that used grub4dos as the boot loader, all the puppy RO files on a FAT partition but the save file on f2fs and it booted and ran perfectly, all devices recognised. No reason I can think of that it wouldn't work on other pups or macs. (macbook pro, imac). F2fs would not be necessary, just FAT and booting with grub/grub4dos.
When I get more time I will go into this further (in another thread).
Posted: Thu 23 May 2013, 22:01
by noryb009
Actually, it might work on bootcamp (maybe only Lion and before, they changed some things recently to not allow XP). According to the Boot Camp
wikipedia article*, "Its functionality relies on BIOS emulation through EFI and a partition table information synchronization mechanism between GPT and MBR combined". So it might currently work, it might not.
* original URL didn't work because of brackets in the URL
Windows 8 support with NLS
Posted: Mon 27 May 2013, 07:22
by shinobar
Hi noryb009,
awaiting your Windows 8 support with NLS for our 550JP, coming soon.
http://shino.pos.to/party/bridge.cgi?pu ... cise/test/
tutorial of installing Puppy linux on a intel mac
Posted: Mon 27 May 2013, 23:47
by don570
Here's a nice tutorial of installing Puppy linux on a intel mac
using the conventional method.
http://www.computerbastard.com/usbmac-puppy/
_______________________________________________________
Posted: Mon 24 Jun 2013, 17:40
by ampersand
I'm new to all this so go easy. I thought I'd give Puppy a whirl on an old laptop using the Windows installer but when I booted up it would always go straight to Puppy with no option to boot into Windows 7.
I ran Grub4Dos From within Puppy which recognised my Windows installation and created an entry for it but when I try to chose that option I either get a grey progress bar which zips to the end and sits and does nothing ("Windows") or a it just boots into Puppy ("Windows Vista/2008/7").
My menu.lst looks like this at the moment, any help would be appreciated.
Code: Select all
# menu.lst produced by grub4dosconfig-v
color white/blue black/cyan white/black cyan/black
timeout 10
default 0
# Frugal installed Puppy
title Puppy slacko 5.3 (sda1/Puppy-Linux-530)
find --set-root --ignore-floppies /Puppy-Linux-530/initrd.gz
kernel /Puppy-Linux-530/vmlinuz pmedia=atahd psubdir=Puppy-Linux-530 pfix=fsck
initrd /Puppy-Linux-530/initrd.gz
title Puppy slacko 5.3 (sda1/Puppy-Linux-530) RAM mode\nBoot up Puppy withot pupsave
find --set-root --ignore-floppies /Puppy-Linux-530/initrd.gz
kernel /Puppy-Linux-530/vmlinuz pmedia=atahd psubdir=Puppy-Linux-530 pfix=ram,fsck
initrd /Puppy-Linux-530/initrd.gz
# Windows
# this entry searches Windows on the HDD and boot it up
title Windows\nBoot up Windows if installed
errorcheck off
find --set-root --ignore-floppies --ignore-cd /bootmgr
chainloader /bootmgr
find --set-root --ignore-floppies --ignore-cd /ntldr
chainloader /ntldr
find --set-root --ignore-floppies --ignore-cd /io.sys
chainloader /io.sys
errorcheck on
# Boot from Partition Boot Record
title Windows Vista/2008/7 (sda1:PBR)
uuid A47464AD74648440
chainloader +1
# additionals
title Find Grub2\nBoot up grub2 if installed
find --set-root --ignore-floppies --ignore-cd /boot/grub/core.img
kernel /boot/grub/core.img
title Grub4Dos commandline\n(for experts only)
commandline
title Reboot computer
reboot
title Halt computer
halt
Posted: Tue 25 Jun 2013, 00:30
by don570
title Windows Vista/2008/7 (sda1:PBR)
uuid A47464AD74648440
chainloader +1
maybe ---> find --set-root
is better???
I had a similar problem a couple of days ago except I had
just installed a version of Ubuntu and my computer would only boot up
ubuntu.
So I took an old CD of Racy (Puppy) linux
and booted up with it and ran Shinobar's Grub 4 DOS
That fixed my menu.lst
_______________________________