Puppy Linux Discussion Forum

LateAdopter · Joined: 27 May 2011 Posts: 148 Location: Reading UK

Hello Snail

When you format media, a new filesystem is written, that's all. No existing data is intentionally erased.

The ISO root directory file entry could be left intact, when you format FAT16.

If you are interested in looking at what is on the media, iBored is a useful free sector editor. It has templates that decode common disk sectors into human readable text.

Snail · Joined: 18 Oct 2009 Posts: 238

Hi LateAdopter,

I did more than just reformat. I used GParted to delete the ISO partition and created a whole new partition the size of the device, then formatted. GParted recogised that there was something unusual about the stick and asked about creating a new partition table and I said go ahead. In spite of that it obviously didn't clear out everything. Probably I did something wrong again. Anyway I cleared out everything using

killapup · Posted: Sun 30 Jun 2013, 07:47 Post subject: FD64 621 not completing boot.

G'day, I've been a happy and content Puppy user for quite a while now but recently came across fatdog and thought I'd give it a go. I've got a few different puppies installed on my laptop, Slacko being my main go-to puppy, love it!!

I downloaded FD 621 and burned it to a CD, put it in the drive and booted...

The start up found the vmlinuz and the initrd files, the second taking an awful lot of 'dots' to load before getting to the kernel booting part.

It got there, to the message 'Booting the Kernel:' and that's where it stopped. I left it for quite a while and tried a few of the different boot menu options to see if any of them would give a better result, but they all hung at the same point.

As far as I can tell, the CD burned ok, I even tried burning a second one at a slower speed, but to no avail.

Can anyone tell me what may be wrong and what I might be able to do to get it to boot? What boot options should I try? I'm not a overly experienced CL operator, I'm not afraid to use the command line but for more complicated operations I need a bit of guidance.

My system is an HP Compaq Presario V2000, AMD Turion64 1.8G processor with 512M RAM and radeon video cARD.

This is the first puppy derivative I've tried that hasn't booted on my system, although since trying FD I found one called Great Dane that also didn't boot, but that's another story. If anyone can help, I'd be grateful, thanks in anticipation.

gcmartin · Joined: 14 Oct 2005 Posts: 4135 Location: Earth

Minor item for development
Hardinfo in FATDOG does not show RAM use on its Computer page (Hardinfo>Computer), yet Barry's Hardinfo does, as seen below.

Both the Raring version and the FATDOG version is reported the same in their Hardinfo>Help>About screens.

Is this an issue of Hardinfo code, LInux kernel, or one of Motherboards?

This is a NON-critical issue.

Here to help

chapchap70 · Posted: Sun 30 Jun 2013, 18:02 Post subject: Re: FD64 621 not completing boot.

chapchap70 · Posted: Sun 30 Jun 2013, 18:43 Post subject: Virtual Machine

Has anyone tried the VirtualBox 2.4 SFS?

I think the kernel is different in 610 so the module won't load in 621. I did not see a VirtualBox 621 SFS so I tried 610. Unless there is something simple I could do, I am thinking I would have to use FatDog 610 so it would load the correct kernel module for VBox.

chapchap70 · Posted: Sun 30 Jun 2013, 19:56 Post subject: Working Now So Far!!!

From the Control Panel, (System) I downloaded kernel-source-3.8.7.sfs after I had previously downloaded fd64-devx_620.sfs and loaded them.

I have been only able to open VirtualBox from within the terminal so I did this again and got the same error I had been getting.

Q5sys · Joined: 11 Dec 2008 Posts: 1047

chapchap70

Q5sys · Joined: 11 Dec 2008 Posts: 1047

killapup · Posted: Mon 01 Jul 2013, 06:59 Post subject: Re: FD64 621 not completing boot.

chapchap70 · Posted: Mon 01 Jul 2013, 07:39 Post subject:

Hi killapup

FatDog was designed for 64 bit computers with lots of RAM. From what I've been told, 4Gigs and up runs noticeably faster than the 32 bit computers/OS'es.

I can't say whether more RAM will make yours work but I am running FatDog on a netbook with only 1 gig of RAM. I like FatDog but it is no faster than Slacko or Lucid on my netbook. I don't know how much extra RAM would cost for your laptop but my netbook cost me $200.

tlchost · Posted: Mon 01 Jul 2013, 07:57 Post subject: Pidgin Problems

I'm using a bootable USB configuration and notice that unlike most puppies, I can not move pidgin's .purple directory our of the save file area to /mnt/home and use a sym link.

Is there a way around this?

Thanks

Thom

killapup · Posted: Mon 01 Jul 2013, 08:11 Post subject:

Thanks again chapchap,

I think to put mine at 1G it was only going to cost about $30 but that was a little while ago and I may not be remembering correctly??? Anyway, I'll consider what I'll do and see if I feel its worth going that way.

Ok cheers, and thanks again.

kirk · Joined: 11 Nov 2005 Posts: 1392 Location: florida

killapup,

You can try booting with pfix=nox and see if it boots to a prompt. I haven't tested with less than 1Gb of RAM, but I would guess 512MB might work. The system will use about 210MB of RAM for storing the kernel and SFS file. Of course you still need RAM to actually run things, it would be tight. We do consider 1G the minimum to run X.

tlchost,

You would probably need to run Pidgin as the root user to do that. It normally is ran by user spot in Fatdog64. Unless your usb drive is formatted with a Linux filesystem and you make sure that spot still owns the .purple file after you copy it, it will not work with spot running it. You can edit /usr/share/applications/pidgin.desktop and change:

Exec=pidgin-spot

to

Exec=pidgin