My 701SD running Antix. I don't have any Puppeee screenshots uploaded yet.

http://i751.photobucket.com/albums/x...creenshotx.jpg

http://i751.photobucket.com/albums/x...reenshot-4.jpg

http://i751.photobucket.com/albums/x...reenshot-3.jpg

Maybe give you incentive/something to shoot for. Once you get your 701 straightend/figured out. Good Luck with it.

Happy Trails, Rok

The root delay trick didn't work. Thanks anyway.

Parted magic on ubcd works with me because it's a RAM only version.

I think my plan now is, go home and use gparted on sda1. Try my usual live usb's to see if any will boot now. If not, then come back and do what you describe above, i.e. a manual install... but the instructions above involve booting a live usb. If I could do that, there wouldn't be any issue. I'd boot live eeebuntu and click the 'install' icon.

UPDATE

I used gparted to delete the partitions on sda1. I deleted both the following:

/dev/sda1 ext2 2.30gb
/dev/sda1 /media/sda2 USER 141mb

Afterwards, the main partition was a single block of 'unallocated' space, of 3.71gb.
The first sector 0 and last 7775459, of a total of 7775460

Left undeleted were:

/dev/sda3 unknown system. It was followed by the symbol of an exclamation mark in a triangle and a black square, had the label BIOS the flag was lba and it was 7.84mb
/dev/sda4, also followed by an exclamation mark, no labels or flags, 7.8mb.

I shut down, tried to restart, the new eee 701 iso installed to usb. This showed the usual unetbootin menu, a 'starting system' message and then nothing.

The live eeebuntu usb was exactly the same, booting as far as '0.336948 ACPI: CHECKING INITRAMFS for custom dists'.

Then I went back to gparted, applied an ext2 label to the primary partition, so it was no longer unallocated, tried to boot both again with the same result.

Notes:

When gparted was doing its thing, the ssd light at the front flashed for a while, something it hasn't done since the trouble started.

When I was looking around sda1 before I formatted it, I noticed a file called BIOS which had a file in called 07121700.EN and showed up as a program. No idea if that's normal or if it's still there or not.

Gparted still shows two little blocks of unformatted space at the right hand end. I'm not touching them because one of them is called BIOS.

The splash screen still comes up OK. UBCD and Parted Magic are still OK. The sdd is still listed/recognised in the bios.

So... I don't know now. Perhaps use unetbootin on ubcd to install something and see what that does, or perhaps nuke, in case there's some file still being read? I don't know.

UPDATE

Trying to install pupeee

I formatted a 2gb drive to fat32, put the files on manually, then let unetbootin put the custom kernal on and I replaced the config file manually.

It booted to a pupee splash, and I tried to boot the default.

It went:

loading /vmlinuz................
loading initrd.gz ................................ ready.

then the writing stayed there, and a cursor appeared at the top right under the L of the first word 'loading'.

Nothing happened. I pressed all the keys on the keyboard and nothing.

Putting Pupee on SDA1
 

UPDATE

Putting Pupee on SDA1

I booted ubcd. Put in the usb key with the pupee files and put them all on sda1, then clicked on the linux installer in the /boot file.

A console came up saying it was doing it, then it said it was done on sda1 and that the drive would be bootable.

I booted with no usb's. Got the pupeee splash, and it booted to the same result:

loading /vmlinuz................
loading initrd.gz ................................ ready.

then the writing stayed there, and a cursor appeared at the top right under the L of the first word loading.

In the advanced option, all choices are the same.

NOTE: I did this without using gparted to delete those little two partitions on the drive, one of which is called BIOS. There was the one large partition 1 formatted to ext2.

Hang on... is sda1 bootable? I have the eee before me. (I'm in a cybercafe, eee on the keyboard ledge and keyboard on my lap, they must think I'm mad).

Oh, I'm looking at it now. It says:

/dev/sda1 ext2 /media/sda1 3.71gb used 198.00 Unused 3.51gb flags: boot.

So, in gparted, the partition is listed as /dev/sda1 but the mount point is /media/sda1 ... of course it is, I'm using UBCD... so that doesn't mean anything.

So... I keep saying it. At least I have parted magic.

Yipee. Yipee.

Maybe I should post all this on a pupeee forum? But already I'm asking for help of four forums. It's the Bermuda Triangle of all computer problems; it's really weird and no one can understand it.

There's some simple answer, and someone out there will know what it is right away. They'll look and say, use this little code or that little hack or type this at the boot prompt.

But I might grow old looking for that person and end up like Mrs. Haversham is Great Expectations.

Look! I'm going slightly insane. I need to count my blessings. I still have Parted Magic. I can do my study. It could be worse.

Oh, one last thing.

When I went to sda1 to put the Pupeee files on, there was a 'lost and found' folder still existing on that drive.

Then again, in the Bermuda Triangle, I guess anything is normal.

UPDATE

I deleted the last two partitions on sda1 last night.

Tonight I'm going for the final solution: nuking.

If that doesn't work... then it's some mysterious hardware issue.

Refer to my answer at eeepcforums. I am beginning to think you are going about making puppeee bootable on sda1 all wrong.

The betas require you be root user in file manager like in parted magic that you are using before you can click on bootinst.sh to make puppeee bootable on internal SSD drive.

gotta be