The description reads: When Legacy Support is enabled, BIOS will load Compatibility Support Module (CSM) to support Legacy OS such as Windows 7, Windows Vista, Windows XP, and DOS. When Legacy Support is disabled, BIOS will boot in UEFI Mode without CSM to support newer OS such as Windows 8."

If I turn Legacy Mode OFF I gather that it will stop MS win7 from loading but will that help or hurt LH64-b2 in any way (perhaps solving the no-boot Frugal problem) or make no difference?_________________Thanks! DavidHome page: http://nevils-station.comDon't googleSearch!http://duckduckgo.com
TahrPup64 & Lighthouse64-b602 & JL64-603

I moved my Lighthouse 64 beta 2 install to an older HP desktop pc.
I booted with the option that doesn't load x and ran xorgwizard-puppy
then chose probe and the correct screen resolution.
I needed to run the multiple sound card wizard and then reboot to get
it to use the usb sound card that I'm using.

Right click on the 'unallocated' partition. This should be the same size that you shrunk your C: drive in Windows.
Select 'New', the Create new Partition window will pop up.
On the File system pull-down menu select 'fat32'.
For 'New size (MiB):' enter 1024. That makes 1GB.
Enter a Label for the new partition, then click Add.

OK, now it looks like you've already shrunk your C: drive and sda4 is a Linux ext3, so you can shrink sda4 by 1 GiB in GParted and then create a new 1 GiB Fat32 partition as above. Yes, this new partition must be Fat32; please do not use sda1 for this new partition, sda1 should be reserved for Windows to avoid problems with hibernation.

Once you've finished Steps 2 and 3 your new Fat32 partition should look like this in ROX-Filer, except that initrd will be initrd.xz and instead of sda8 will be sda6 or whatever GParted uses for the new partition:
In Step 4, change:

Quote:

options "pmedia=atahd pdev1=sda7"

to

Quote:

options "pmedia=atahd pdev1=sda4"

Quote:

Also, when the Frugal setup requested a name for the MS win7 partition in refind.conf (it actually assumed win8) I entered sda1 because I didn't see the NEB (?) or SYSTEM label anywhere.

Click on the Drives icon on the desktop of LH64 to find the label of sda1, I don't know what HP uses.

edoc wrote:

In BIOS System Configuration the ]Legacy Support is Enabled.Could Legacy Mode - Enabled - be interfering in some way?

CSM is good I think, that's what I'm using here. But you can try either way and see what works best for you.

Quote:

I hope to never use MS win7 so it's not a problem should I have to stop & edit BIOS should a rare need arise - I really want LH64 to work!

More info ... the Boot Manager Options are:

USB Hard Drive (UEFI)

OS Boot Manager

Boot from EFI File

That's it! In Step 5 of the UEFI Install, use 'Boot from EFI File' to add the new boot option, which will start the a LH64 (rEFInd) boot menu from the new Fat32 partition.

Quote:

Generally on the boot tab you will find some way to add a new boot option. After you find the button to to add a boot option, you will be asked to select a partition. This is kind of cryptic as well, and might take some guessing. Then you will be asked to browse to a bootable EFI application, this will be EFI/boot/bootx64.efi on your new fat32 partition. If you can't browse to that path or you can't see the files that you put in your fat32 partition under EFI/boot/, you probably picked the wrong partition. After you have added your new boot option, move that new boot option to the top of the boot order. Again, this will vary with different UEFI implementations. Then save and reboot.

No, only Wine (windows apps) should be 32-bit, and only if the optional Wine SFS is loaded. Better to use a 32-bit OS if you need the older apps.

Are there any options for me to run 32bit stuff in LHP? I don't want to run any of the 32 bit releases, because I've had driver issues with them. LHP works great on my laptop. Can I take parts of the slacko release and add them into LHP?

refind.config should be in the FAT32 partition I have labeled lh64b2 - yes?

BUT ...

Should the partition pointers in refind.conf for LH64 be sda4 or lh64b2?

Right now I have them pointing to sda4.

NOTE: One of the lines to which I refer reads ...

Code:

---->options "pmedia-atahd pdev1=sda4

Should it rather read ...

Code:

---->options "pmedia-atahd pdev1=lh64b2

Looking at this discussion of refind.conf I am uncertain which is the 'normal boot partition'; sda1 only contains a folder labeled "EFI" and a file labeled "grldr" whereas sda3 contains all of the MS win7 files and folders.

If you have problems with refind not finding the ESP partiton when booting , it may show an error like bootmgfw.efi not found. You can try changing volume from ESP to 0: (That's a zero and a colon. The zero represents the first partition. If the normal boot partition is on sda2, then you would want "volume 1:".)

Understanding that LH64 does not run native linux 32bit apps with any reliablilty, and understanding your need, this might help:

VirtualBox

KVM-QEMU

If you are not familiar with either, what they do is allow you to "boot" an additional PC (virtually) in the running LH64. When you boot the additional running PC within your lh64 you can start and run linux 32bit apps in that virtual PC while the LH64 is running its 64bit/Wine(windows) apps.

There is several Puppy threads on VirtualBox. FATDOG64, in its recent version, added QEMU-KVM, OOTB. LH64 has always offered VirtualBOX as an add-on.

Hope this helps, as, its the manner that I have been running a 64bit Linux OS and a 32bit Linux OS on the same PC harmoniously-together simultaneously._________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Enginesor use DogPile

Understanding that LH64 does not run native linux 32bit apps with any reliablilty, and understanding your need, this might help:

VirtualBox

KVM-QEMU

If you are not familiar with either, what they do is allow you to "boot" an additional PC (virtually) in the running LH64. When you boot the additional running PC within your lh64 you can start and run linux 32bit apps in that virtual PC while the LH64 is running its 64bit/Wine(windows) apps.

i have heard of virtualbox before. ive never heard of that 2nd one. from some googling it looks like virtualbox is completely separate from the rest of my system. its like its in its own little, box, for lack of a better word.
is there some way to make it work so I still have the ability to get to my files on the rest of my computer from inside the box?

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum