thought I would have a go at an Alpha of Photon (based on the pre-alpha 2.20)
http://tmxxine.com/Wikka/wikka.php?wakka=LinuxTmxxinePhoton

I set up murgalua, xbasic, python and the dev-220.sfs as a test.

Just before running Dougals remaster script, I thought it best
to save my settings (I was running from CD with the

Code:

puppy pfix=ram

option

Much to my surprise on the reboot, all kinds of save files
were available from sub directories (this is a known upgrade in 2.20) and even an external USB hard drive . . .
but where was the file I had just saved? . . . maybe I made a mistake - settings lost

No matter - it is a bit early for Photon

However . . . I do find the multiple save files VERY useful but for the life of me can not remember what is what.
It might already have been suggested that we are offered a variable name?

eg. What is the name of this save file? (press enter for default)
In this way Aunty Maude, Rufus the dog and LinuxBoy can all have a save file with a specific and memorable name.
I of course can use names like 2.20_Happy_Photon_test

Hi Barry, new Pup looks good. One hiccup so far. On my install it sits and waits for 30 seconds after this line "Input: usb HID V111 mouse on usb 0000:00:0a 1-2" ....... (or there about I can't read my own writing!)
Any chance of an easy way to enable full debug O/P on boot for us "techies?" to fiddle on finished Pups?
1440*900 24 Bit worked flawlessly from start (Never got it to work before, excellent)
Atols nice, hope it stays.
DHCP seems quicker but perhaps you could try backgrounding it again?
Boot time on Althlon 2ghz (xp3200) 512 RAM (Installed on a SATA partion Frugall) 36 seconds
Many many thanks for your hard work.
Tony

Looks like a problem with Xorg. Fonts look fuzzy. Some letters are fuzzy. It seems like parts of letters "hit between pixels". I hope it is clear what I mean, I do not know what is a scientific word for it. At first I thought I set wrong resolution. But upon checking it, resolution is set correctly.

I was able to correct this by adjusting the "pixel clock" setting of the monitor. This is a hardware setting. The monitor has small buttons, which activate the menu. The pixel clock is under "Image settings". So, problem solved for me. But it is strange that Xorg does not set this automatically.
Dell desktop, with Dell LCD monitor 1280x1024

Actually, I had this problem before, but less severe. What I had before was incorrect positioning, both horizontal and vertical. I observed a very strange phenomenon. I have two computers, a laptop and a desktop. Two very different machines, different screen resolution. Never had a problem with the laptop. It is the desktop Dell that first gives incorrect monitor settings. I run Puppy from USB flash, the same Puppy on two machines. The strange thing is, if I first boot Puppy on the laptop, then I later do not have any problems on the desktop. After running from the laptop, desktop monitor settings come out right the very first time.

Generally my fonts look OK but the text in the startup background is fuzzy. The image looks OK when viewed in mtPaint at 100% zoom. The anti-aliasing is causing the problem, but I don't really understand why. I have been experimenting doing screen captures of text, the images look fine in mtPaint and qiv but the anti-aliasing is fuzzy when used as a desktop background.

Not a big problem, and don't want to dwell on it here. I just wondered if someone knew why? I suppose I should repeat tests in an earlier puppy._________________Will
contribute: community website, screenshots, puplets, wiki, rssEdited_time_total

HairyWill : Dunno for sure why we need to kill wavplay - it was in the original script that I converted to use Gnocl. It does the bark sound on first boot and there was a note saying that on some machines it wont shut up with the yapping.

Anyone having problems doing a pup_save resize.
I'm sure I managed one as my pup_save is 96MB but now it fails.
Here is the output from the tool that creates the resize file

Quote:

Okay, you have chosen to increase pup_save.2fs by 131072 Kbytes,
however as the file is currently in use, it will happen at reboot.

Technical notes:
The required size increase has been written to file pupsaveresize.txt,
in partition ext2 (currently mounted on ).
File pupsaveresize.txt will be read at bootup and the resize performed
then pupsaveresize.txt will be deleted.

You can keep using Puppy. The change will only happen at reboot.
Click OK to exit...

It doesn't seem to know where /mnt/home is. The pupsaveresize.txt file gets written to / instead of the top level of the partition.

I've had a look at /usr/sbin/resizepfile.sh
Has the format of PUPSAVE in /etc/rc.d/PUPSTATE changed because the SAVEPART variable is being initialised to the partition type instaed of its location

The facts:
1.- I dont have hardisk
2.- I have 1.5 GB memory ram
3.- Always I work with a multisession Puppy disc (CD or DVD)
4.- I load puppy 2.20Alpha iso from a multisesion format disc. No problem.
5.- I configure country, xorg, and net server. No problem
The issue:
When I try to reboot, It supossed to ask for record the changes on CD... but
when start the routine record messages, finally It start to ask for a NEW CD, because the used one is full, and IS TIME FOR A NEW DISC.
What is happening ?
It is a bug ?
It is my fault or I miss something ? (again).

...Generally my fonts look OK but the text in the startup background is fuzzy. The image looks OK when viewed in mtPaint at 100% zoom. The anti-aliasing is causing the problem, but I don't really understand why. I have been experimenting doing screen captures of text, the images look fine in mtPaint and qiv but the anti-aliasing is fuzzy when used as a desktop background.

Not a big problem, and don't want to dwell on it here. I just wondered if someone knew why? I suppose I should repeat tests in an earlier puppy.

I noticed that too. I used mtPaint to add "2.17" and "2.20" to the bird background. It looks sharp in mtPaint but fuzzy on the desktop. I guessed it was something to do with jpeg compression but didn't investigate any farther.