Search Results for 'grub4dos'

[Moderator christophe]

@seaken64
The grub4dos drive can be FAT16/32 or EXT2/3/4. It needs no “host” OS, so it’s perfect for frugal-only OSes.

@woodlark
As James Taylor once sang: “That’s why I’m here.” (Just my way of supporting MY operating system.)

• This reply was modified 4 years, 1 month ago by christophe.

confirmed antiX frugaler, since 2019

[Member seaken64]

Ok, that is a good solution. I have used AirBoot in the past to do something similar with OS/2 and antiX. Good to know Grub4DOS works as well.

Seaken64

[Member seaken64]

Glad you got it sorted. So your solution was to use Grub4DOS? Where is the menu.lst file kept? Is that kept on the first drive, the Windows drive? Then is has to be FAT32?

Seaken64

[Member seaken64]

woodlark wrote:

Thank you all for your replies. This is disappointing. One of the reasons I decided to install Antix was the frugal install option. I have used Puppy Linux in the past, and came to love the idea of a frugal install. Puppy always included Grub4Dos when installing. Unfortunately, the current crop of puppies doesn’t serve my current needs.

I’m going to have to consider what I really want to achieve. Windows is not really needed, but it happened to already be locate on that computer. I suppose I could replace it with another linux (just to get a bootloader installed). Otherwise, does anyone know a way to manually install grub2 from inside antix?

Is there enough room on the hard rive to partition for an antiX install and keep Windows where it is? I do this a lot on old XP or Vista systems. I’ll run Gparted from the live antiX and shrink the Windows and leave anywhere from 5 to 20 gig for antiX depending on the size of the drive. I then start Windows and let it check the disk and re-set it’s disk table information. Sometimes it will be necessary to repair the Windows but usually it is not needed. Once antiX is installed it will write the grub to launch Windows. I know you wanted a frugal install but this is the way I do it to get both Windows and antiX to boot from grub.

You may be able to use the Windows boot loader but it is harder to accomplish for me. Or just use a boot CD.

Seaken64

[Moderator christophe]

If you like to run antiX frugal-only & have a puppy linux disk/usb, you can:

1. do the frugal antiX install
2. boot up puppy & run the grub4dos installer. It will detect antiX (and maybe “bark” about finding no puppy files, but it should continue anyway).
3. Once done, manually edit the menu.lst, since puppy will only write the basic skeleton needed to boot – no boot options for antiX (except “ro” — “read only,” which you should erase). (I’ve added a menu.lst antiX entry below that I use on an “antiX-frugal-usb,” – use as reference, if needed).
4. It SUPPOSEDLY will allow you to boot Windows also, if installed, BUT I DON’T HAVE WINDOWS so I have not tested if this part works. (If your Windows becomes unbootable, don’t get mad at me!!)
5. One note on my antiX entry: “root=(0,1)” means the boot drive where grub4dos resides (0), and that drive’s 2nd partition (1). (The grub4dos boot drive is always 0, whether booting from usb or hdd.) And my antiX directory was renamed to just “antix” to keep it simple. The rest is probably self-explanatory /regular antiX boot parameters:

# antix 17.3.1
title antiX Linux 17 Frugal-Persistence
uuid 14d9effb-fc66-45ac-b738-7f00b0c69416
search –no-floppy –set=root –fs-uuid 14d9effb-fc66-45ac-b738-7f00b0c69416
kernel /antix/vmlinuz root=(hd0,1) bdir=antix buuid=14d9effb-fc66-45ac-b738-7f00b0c69416 vga=788 persist_static tz=America/Chicago quiet splash=v
initrd /antix/initrd.gz

[note, the line starting with “tz=…” is actually the continuation of the previous line (“kernel …”)]

Hope this helps.

• This reply was modified 4 years, 1 month ago by christophe.
• This reply was modified 4 years, 1 month ago by christophe.
• This reply was modified 4 years, 1 month ago by christophe.

confirmed antiX frugaler, since 2019

[Member woodlark]

Thank you all for your replies. This is disappointing. One of the reasons I decided to install Antix was the frugal install option. I have used Puppy Linux in the past, and came to love the idea of a frugal install. Puppy always included Grub4Dos when installing. Unfortunately, the current crop of puppies doesn’t serve my current needs.

I’m going to have to consider what I really want to achieve. Windows is not really needed, but it happened to already be locate on that computer. I suppose I could replace it with another linux (just to get a bootloader installed). Otherwise, does anyone know a way to manually install grub2 from inside antix?

[Anonymous]

While waiting for someone who is familiar with grub4dos to notice this topic,
you may find a soution mentioned in prior similar discussions: https://www.antixforum.com/forums/search/grub4dos/

Hola:Soy nuevo usuario en Antix la cual quiero probar , aunque llevo varios años usando microdistros linux como son :Puppy, Slitaz, Slax, Porteus, con las cuales he trabajado feliz.

Actualmente tengo una laptop con un disco con tres particiones y otra mas de swap (6gb) La memoria ram es de 2 gb. En la primera partición tengo una variante de Puppy instalado de manera frugal y que arranca con Grub4dos.

En la segunda partición quise instalar Antix de forma frugal de hecho como se ve en la primera imagen que adjunto el cd grabo una serie de carpetas y archivos Pero eso no se reflejo en el menu.lst de grub4dos y por eso no hay forma de arrancar Antix.(muestro imagen de mi menu.lst)

¿Como modifico Menu.lst o que tengo que hacer para tener las dos opciones?

Attachments:

1. 

   sda2conantix.png
   

2. 

   menulstgrub4dos.png
   

Hi all,

i want to know how to install frugal Antix at 2nd partition.
with YUMI, i already frugal install tinycore and xenialpup at 2nd partition(ext4) and boot with grub4dos. so how i install Antix/MX on the same partition without change
label partition or format it? ok i change label partition to antiX-Frugal boot antiX(using yumi live usb) and f5 install to 2nd partition, but now to boot to antiX frugal, i still using yumi(f5), how can i using grub4dos direct boot to antiX frugal folder at 2nd partition( maybe some pointer/code for chainload because i see inside folder there is syslinux and grub)

• This topic was modified 4 years, 7 months ago by benperkasa.

Recently did a frugal install of antix 17 to the hard drive of a cheap Walmart HP laptop. I run antix on a couple of old computers. This one wouldn’t let anything install because of UEFI issues. Peppermint, Zorin, Antix17, Sparky either crashed or couldn’t find sda1. Using grub4dos installed antix17. Does great, has persistence, really fast. But I’m a nooby I guess. Do I need to somehow watch the persistence folder size? Sorry I’ve tried to research I little bewildered.

[Member crestiah]

@736b69646f6f maybe i miss-understood dolphin_oracle previous post and thought it was a 2 stage boot process sorry.

think the problem was with the fujitsu not the lenovo
think the fujitsu is 64bit capable but not recommended kind of like my lenovo g575 (1.3ghz procesor, 8gig ram, doesnt like systemd either at least as a desktop anyway).

in terms of the 2 stage boot i was thinking of (passing the buck) syslinux wouldnt need to know what uefi is capable of only to launch it. (hence passing the buck to uefi/grub2 to take-over booting operations/capabilities)

kind of what an acquaintance at puppylinux would do with grub4dos went something like (cant remember the exact command write up but hopefully you get the drift)

Title whatever .iso /.img file
root= (hd0,0) \boot\whatever.iso
boot = \boot\grub\whatever.iso
initrd = \boot\initrd\whatever.iso

anyway the idea was to lock/jail root to the start of the iso/img file, so anything you did or saved stayed inside that img file. as well as bypass the dos memmory limits.

• This reply was modified 4 years, 11 months ago by crestiah.
• This reply was modified 4 years, 11 months ago by crestiah. Reason: left out a word or two
• This reply was modified 4 years, 11 months ago by rokytnji.

[Member crestiah]

the 5 minute blank screen would drive me barmy.

questions
what usb rating are the usb sticks and the ports they are plugged into? usb1, usb2, usb3, usb3.1, given the read, write, transfer rates this could make a bit of a difference especially if you are coupling them with a usb port rated for usb1 as an example.

1 computer is a dual core but what is the cpu speed, the other a quad core whats its cpu speed? surely this would add a difference to the boot up time.

i dont know much about the uefi/gpt thing, but the impression i get from this thing is that it acts more like a save state. the equivalent on a bios/mbr would be hibernate/sleep mode. at least this is how i look at it.

i dont know anything about grub2 so not sure how that operates, grub4dos had some quite interesting ways of doing things though.

i wouldnt think an “if then do” statement (ie if bios/mbr then boot syslinux but if gpt then boot uefi) would take upto 5 minutes to process, but i suppose it might if grub2 is geared more towards a uefi boot than a bios boot, maybe its taking 5 minutes to reprocess the commmands to be acceptible to bios boot?

• This reply was modified 4 years, 11 months ago by crestiah.
• This reply was modified 4 years, 11 months ago by rokytnji.

[Member crestiah]

I’d Be curious to know if this worked with hybrid iso’s

hybrid = cd/uefi booting

puppy linux had a great little multi-boot usb I just cant remember which puppy it came from or the particular script/package it was.
you could how ever drag n drop cd based iso’s, as many as you liked that fit on it.

however for some reason anything with a hybrid style on it seemed to come up with a grub error code =60 “must be a continuous disk”

my pre-sumption is that it had something to do with either the uefi style booting or persistance ability just not sure which.
as an example i can run calculate 17.6 for i686 however i cant run devuan 2 ascii i386 from it.

after re-examining the puppy multiboot usb found it was based on grub4dos with some auto menu.lst rebuild scripts. i cant read the rebuild scripts, however it probably needs a new entry to rebuild for grub2 start-up.

given the simple beauty of grub4dos i can understand why they used it.

• This reply was modified 4 years, 11 months ago by crestiah.

[Member stevesr0]

Thanks for the additional information.

The system I am going to wipe off has become encrusted with several bootloaders chained together over the years for different distros.

I have grub4dos, syslinux and grub2 (and perhaps one other one that I can’t bring to mind at the moment). Don’t currently have LILO on this system.

I am looking forward to a simpler setup.

Steve

[Member bobbiecb]

anticapitalista wrote:

Is 2 a Grub4Dos issue?

Here’s what I learned…
It appears that ext4 has certain advanced features that many products do not yet support. Apparently antiX uses one of these new ext4 features.

I found that neither Grub4Dos or Grub Legacy will read the ext4 filesystems supported by distros that use the new feature. (I didn’t test with Grub 2 so I don’t know the story there.)

When those two Grubs failed, I immediately tried to verify the filesystem with es2fsck — only to find it didn’t work either. It was in locating and applying the latest upgrade to e2fsck that I came to understand the problem. After the upgrade to e2fsck the filesystem checked out fine.

The new feature is called “metadata_csum” and is described perfectly in this thread — http://dev1galaxy.org/viewtopic.php?id=771
That thread shows the exact error message I received from es2fsck on the antiX partition before I upgraded my e2fsck.

For me, the easiest solution was a work-around. Avoid the issue by installing antiX into a non-ext4 partition (like ext3). Then you can use any version of Grub you want, no problem.

Thanks for your feedback. I’m having lots of fun with antiX! It flies on my old AMD 3800+ box. Very cool.