Flash, I haven't tested multisession yet -- that was something that missed out due to my time constraint, leaving for my holiday.
But, I'll give it a high priority, will work on it while on my "holiday"

I used gparted to delete all partitions (except the swap partition,which was locked) on my 4G HD and then to create a new ext2 partition. After deleting the swap part. with cfdisk, I also attempted to create a new swap partition. Both attempts failed as I described above.

To create the partitions, I used cfdisk, but needed gparted to format them, which failed. So I used mke2fs and mkswap for the formatting. Then I was able to install -- and find the other problems I reported.

I have been able to do this in previous puppys. It is the most basic way to set up a HD -- an ext2 and swap partition. I ran gparted from the command line, too, but did not see any revealing messages.

The PC is an Aptiva (400MHz, 160MB) that I have used for puppy testing for nearly two years.

PS: Thanks for the link to the Tom Price site! Through you, I am learning everything I know, so far, about Western Australia. Interesting place.

Puppy 216 alpha seems to be noticeably quicker than 214, when programs first start

Yes, seems that way to me as well. I think its AUFS. When I tried Nathen's AUFS package with 2.14 it seemed faster too.

Quote:

Through the network wizard, I can't configure the interface.

The network wizard is missing the folder /etc/WAG. I'll attach it to this message.

I'm sure there are some bugs that still need to be squashed, but 2.16 looks like it will be a giant step forward from 2.14. There has been a lot of changes since 2.14, AUFS, init, NTFS/Fuse, just to name a few big ones. This seems like a pretty solid alpha to me.

First, this is another positive comment on 2.16alpha. I continue to have no problems at all with it, at least on those things I use.

Oh, while I'm feeling humble enough to ask dumb questions, there's the mysterious subject of white out files, the accumulation of which 2.16 is expected to diminish. Pfind says I have about 50k of them. What does this mean?

HenryLast edited by Henry on Fri 27 Apr 2007, 16:47; edited 1 time in total

I have little experience with video, but I've never liked Gxine. Mplayer has performed much better for me, and VLC looked nice (though it was glitched, but that was probably my own fault for using it in a Pizzapup pre-alpha...).

As for whiteout files, they are what makes things that come with Puppy by default disappear when you delete them, since they're actually read-only and can't truly be deleted. Like using whiteout on ink, a whiteout file hides the data from Puppy, so it thinks it's deleted even though it isn't.

There are glitches with them though, especially if a whiteout file tries to hide a directory, then you install a .sfs file that has that directory also. It get's unioned under the whiteout file with the original and never turns up. At least, that's what I think happens. I haven't been paying a large amount of attention to the situation (more concerned with angular momentum, vector fields, and MIPS at the moment, as finals are next week )_________________Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

As per Barry: Should only get a Save button if boot from Flash drive (or multisession CD).

I am booting from a 2.16Alpha closed CDROM with a USB attached hard drive. With this configuration I am always getting the "Save Button". On first shutdown I created an encrypted pup_save file to the USB attached ext2 file system. After rebooting, I had a working pup_savexxxx.3fs encrypted file but still have the save button. Looks like Puppy thinks the external USB hard drive is a USB flash. Also, I get the saving RAM to the PUP_SAVE file message fairly often. This should not happen if puppy thought the PUP_SAVE file was on a hard drive, correct?

I don't think there is anyway to tell the difference, for certain, in code. The USB class/subclass/protocol seems to be rather unrespected by hardware makers. There is a place for them, but my drives don't seem to fall in line.

2.16alpha running very sweetly on the whole.
Dell laptop Latitude C400 with Intel 82830 graphics. Xorg shows only 640x480 resolution possible; shows i810 as driver; xvesa starts with 640x480. Editing xorg.conf to include mode 1024x768 allows display to operate at native resolution.
The wireless wizard has lost its ability to save and load a profile for my wireless. Wireless works fine if "use this profile" is selected.

But now a comment that may be out of place here, which has nothing to do with 2.16 per se. It's about the "default" player Gxine. Back in some of the early puppy versions it did work with a few of the "media" menu items. For the last half dozen or so versions it's been a total loss for me whether as a standalone or browser helper.

Henry

Multimedia is important and Puppy is a composite of the programs it contains.
Part of my problem (a sort of scrunched rainbow effect on the top of playing vids).
Solved by changing from the internal graphics, which uses shared ram - thus freeing ram, to an nvidia card._________________Puppy WIKI

I found the same difficulty as rerwin. All attempts to create and format new partitions on a laptop hard drive failed when using Gparted in Puppy216-alpha. Pulled out of 216 without saving and booted from 215. Gparted performed perfectly.

Has anyone verified that "pfix=ram" works now? I might get a chance to download it today, so I want to make sure it won't mess up my existing pup_save files..._________________What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind

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