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

barry it wouldn't even finish booting in virtualbox and the md5 checked out it got stuck at pivot root and was slow in the other parts also i just tried to run 2.17.1 in virtualbox and it stops at creating unionfs maybe the kernel is to blame not sure

No, the 2.20alpha has the latest, 2.6.21.5 kernel. I have a future plan to *also* release a 2.20 with the older kernel.

I see, so it is not the kernel. I wonder what it could be then. As I said, this problem existed for the orinoco_cs driver before, but in 2.17 it was fixed. The eepro100 has always worked just fine in the past.

I never figured out what caused it before, so I doubt I will be able to find out now (it might not even be caused by the same thing). However, I full confidence in your ability to fix it, Barry._________________Be brave that God may help thee, speak the truth even if it leads to death, and safeguard the helpless. - A knight's oath

I booted 2.20 on my old P II computer, 192RAM (1999 vintage) using pfix=ram. For the first time with puppy, I was able to use XORG instead of XVESA on this computer, though the difference in graphic quality wasn't particularly noticeable. However, I couldn't connect my network or access the web. The wizard failed to find a driver. I remembered that older versions found something called "tulip," so I tried that manually, but no luck. And no luck with any of the other drivers offered (I didn't try all of them).
I booted up a newer computer (P IV, 1G RAM, 2006 vintage) with pfix=ram. This time, XORG configuration led to a blank screen (the monitor just cut out). VESA was fine. Everything else worked; I'm using 2.20 now to write this).
Bootup on both machines was a bit slow, with a "fail" at "switch root" and a 60-second pause.
I hope some of this is helpful.

Tried compiling the synaptics module, missing many headers Xi.h etc. Anyone know where to get all of the Xorg include files? Been looking for a binary, no luck so far. Hard to live without synaptic. Thought 2.17's desktop ikons looked sharper. The spell checker in SeaMonkey is VERY NICE. I kant spel.

Burniso2cd seems not working. When I click the program from Menu--->
Multimedia, it pops out a window asking me to choose CD or DVD. After
I chose my burner, it pops out another window with a lot of messages.
Am I doing something wrong?

I downloaded two modules and renamed them
to .sfs files and used BootManager to load them
at bootup. Tried two games, couldn't figure out
one of them. LTris works pretty good. You might
need the SDL libs for a lot of the games.

Burniso2cd seems not working. When I click the program from Menu--->
Multimedia, it pops out a window asking me to choose CD or DVD. After
I chose my burner, it pops out another window with a lot of messages.

I discovered that this morning. The culprit is the 'cdrecord' program. There is a line in burniso2cd that runs 'cdrecord -scanbus', and certain information is extracted from that, except that pup 2.20 has a recent version of cdrtools (the package that has cdrecord) which outputs information in a different format than the version used in earlier puppies -- which stuffs up the script.

One really annoys me is that it isn't even a minor number change in cdrtools, just a different alpha-version-number. It is so, so annoying.

BAD DOGGY
booted my manual frugal install in the root of the partition
got offered a choice of pup_saves
chose 0 none
when shutting down
invited to create a pup_save
chose the boot partition that already had a pup_save in its root
the existing pup_save.2fs was overwritten
If I had anything in it I would have been upset.

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