Just-Lighthouse64-603/604

[Dry Falls]

Is it possible to boot from a USB stick but store the operating files on the laptop?

Absolutely. A manual frugal install. Merely drag (copy) your L64-602.sfs and, if you have a save file, move/copy the pupsave onto the hdd /partition. Be careful to change/delete "pmedia=usbflash" (if it's specified in the grub/isolinux config file) to "pmedia=atahd" although lighthouse should be able to find them without any pmedia=x parameter.

df

[edoc]

That's the way I've always loaded Puppy - frugal - except on this machine.

I was wondering if an odd UEFI might have made keeping it all on the USB stick necessary for any reason?

It was a long time ago when someone created the lash-up that allowed me to boot Puppy on this laptop at all.

Handling UEFI has some a long way since then.

I'll give it a try a little later today.

Thanks!

[Dry Falls]

copy your grub/isolinux.cfg and system files to the hdd. parameter

Code: Select all

pdev1=sda<your drive #> pmedia=atahd

rename grub.cfg and/or isolinux.cfg files on the usb stick so they're not used. Reboot as usual. uefi should find the config automatically. The stick will only be used to boot the computer, not to load puppy.

[mikeslr]

Hi edoc,

If you want to keep your SaveFile as JLH's equivalent of Pupmode 13 --I think it shows up as Pupmode 15-- after you move your bootfiles from the USB-stick to the hard-drive, you may be able to by adding the parameter pfix=noautosave at the end of your kernel argument.

mikesLr

[gcmartin]

The update feature offers the old and wrong version of QEMU for JLH.

May want to change it reference the 64bit version AND you may want to use the upgraded version. The 64bit version should make better use of the hardware that LH run on. The upgraded versions 2.4+ has couple fixes and new features.

In case there is confusion, 32bit versus 64bit version of QEMU, both versions allow an emulation of any of the platforms allowed by KVM kernel support.. MikeB's "Launcher" allows the users to target ANY virtual PC; thus it can target ARMs, x86-32s, x86-64s, etc hardware emulations.

My past KVM experiences seems to provide a better "feel" with 64bit.

[Dry Falls]

GCMartin, can you provide a link? Maybe this is the reason I've had nothing but problems with Qemu? It's been up since the beginning and I was hoping someone would set me straight on it. The only other version I have (a 64bit) is run entirely from the terminal and I thought that was a bit complicated.

thanks,
df

[Dry Falls]

Found Qemu_Control_Center-0.6.pet (just the gui script + application) on my hard drive and incorporated it into my x86_64 qemu sfs addon. worked good first try, so just uploaded the new sfs to gdrive:

qemu-2.0.0-x86_64.sfs
md5: ecc86823ffeadbb972867a166e7496a5

find the icon in menu -> Utility -> More Utilities

Okay, you're right. Way cooler than vbox.

df

[Dry Falls]

Delta patch (64M) for iso (150908-JL64-603.iso___150918-JL64-603.iso.delta). See op.

[edoc]

Delta patch (64M) for iso (150908-JL64-603.iso___150918-JL64-603.iso.delta). See op.

I don't see a

150908-JL64-603.iso

at Google Drive.

[gcmartin]

604

[edoc]

604

604?

I'm confused ... again ...

[Dry Falls]

I don't see a

150908-JL64-603.iso

at Google Drive.

Sorry. Spaced out on the opening post. Decided not to go with consecutive patches and when I uploaded the last iso, I removed the previous (to save space). There was also a blunder with sven in the patch you were looking for but I caught it and removed it from gdrive. Fixed OP now.

@gcmartin, good idea, but I'd (and so would y'all) have to rename all the sfs files to accommodate. There's a few good reasons to have distro-specific sfs names, and since there's a complete compatibility between previous and current versions of 603 as regards the functioning of those addons, the change will only be cosmetic. I think an upgrade of gcc and glib warrants it, but not merely a new kernel and bug fixes. Of course, by that logic, 602f should have been called 603 and we'd already be playing with 604.

df

[edoc]

I'm still unclear as to what to do to acquire the latest ISO plus Patch.

I don't see any ISO dated for September 2015.

Most recent appears to be "150820".

Do I have a local buffer problem preventing me from seeing "1509xx"?

Delta patch (81M) for iso (150920-JL64-603.iso___150918-JL64-603.iso.delta)

[Dry Falls]

whoops again. 150920 would have been in the future! we're looking for 150820-JL64-603.iso to patch. This delta file supersedes the one uploaded 9/08 ('150820-JL64-603.iso_150908-JL64-603.iso.delta') which is obsolete and will shortly be removed.

[edoc]

Is this what I need in the boot folder - or is some of it unnecessary?

It came out of the 150820-JL64-603.iso

[edoc]

I booted the newest version from DVD.

Moved all of the existing old LH64-associated files to folders.

Copied all of the new JL64 files (see above) in their place.

Created a boot USB stick.

Rebooted & the USB stick was ignored by this laptop.

This is what is on the old USB stick - that has worked all this time.

[Dry Falls]

Created a boot USB stick.
Rebooted & the USB stick was ignored by this laptop.

What did you use to create the usb? There are two universal installers on JL64 plus unetbootin. They all differ substantially. Obviously your original was built with lighthouse universal installer, which creates three (if 'fixusb' is used) partitions. That doesn't work so well on some machines, but apparently you had success with it once.

Also, is your boot menu grub2 or syslinux?

df

[edoc]

I booted the latest version from DVD.

I used the first USB boot disk selection I saw via Menu - Setup

This is what it wrote to the USB stick (I presume that means "syslinux")?

[Dry Falls]

From menu -> setup, scroll down to 'Lighthouse Universal installer' which is what you originally used (judging from the screenshot). menu -> setup->Puppy universal installer-alt is the woof-ce pui and would normally be preferred.

df

[edoc]

OK ...

Booted from DVD
Used Puppy Universal Installer
Left it as VFAT
MBR Default
gparted - wipe
Don't copy .sfs to ram
**BIOS ignored USB stick & booted to ms version of windows (never used, just there in case of some bizarre proprietary emergency)
**If I stop BIOS boot with "esc" and choose "F9" then manually choose the USB stick it boots to Puppy from USB
[NOTE: It appears to be running from the USB stick - I want only to bypass UEFI & to boot to my Frugal install on the HDD)
----------------------------------------------------------------
SECOND TRY:
Booted from DVD
Used Puppy Universal Installer
Used gparted to change to ext3
MBR - sys-nopart.mbr by Just Greg
gparted - wipe
Don't copy .sfs to ram
**Same result as first try
----------------------------------------------------------------
This thing has a weird UEFI.

Is there anything from the USB stick that works that I might open and post that might shed some light as to why it works and these two tries failed?