OFF TOPIC
I'm surprised these incremental versions aren't being additionally offered via Xdelta patches (as opposed to only full-size ISOs), to really reduce the download time for the majority of users, who'll already have a previous alpha.

Is there any application or script that needs that? Or is it just something that you yourself find a useful thing to have? I think it is small, I could put it in.

Quote:

xine takes 20-30 seconds after the button is clicked before it makes any sound from an audio CD. During this time the disk is spinning. This drive worked much quicker in 301. I tried starting xine after replacing the boot CD with the audio CD but then the xine window title says 'There is no MRL'. Even when I put the Puppy cd back into /dev/hdc.

The volume control in the panel has no effect on the sound coming from xine.

Maybe I'll go back to Gxine, same as 3.01. Then at least Dingo will be no worse than 3.01.
I experienced a problem with Xine-ui a couple of days ago -- when I tested a VCD, clicking the "VCD" button on the GUI interface hung my computer._________________http://bkhome.org/news/

Barry,
I created an alpha6 fix for xorgwizard with my report of issues quoted below. Since it was skipped, I have merged the xorgwizard changes into the aplha7 xorgwizard. The result is attached along with a difference listing. I have tested it successfully with both 3.98 and 3.02.

Those changes correct the video adapter signatures for Trident CYBER adapters, add two more of them, and insert the xorg.conf "PreferredMode" monitor parameter to ensure the selected resolution is set. The incorrect resolution may be related to either the new version of xorg or to RandR-enabled video drivers such as "intel".

Quote:

Posted: Mon Feb 11, 2008 8:03 pm Post subject: XorgWizard sets wrong resolution with new "intel" driver
Subject description: New driver supports RandR; ignores Puppy's resolution settings; uses non-listed 1152x864. Solved.
On my IBM NetVista PC with Intel 845 built-in graphics and an ADI 5P CRT monitor, the old driver, i810, set resolutions as directed by Puppy's xorgwizard in xorg mode. In alpha6 and the newer driver, intel, the resolution is set to 1152x864 no matter what I select (1024, 1280, 800) with the wizard. The resolution is reported by HardInfo and corresponds to what I see on the screen.

I found a post that suggests the solution:
http://www.mp3car.com/vbulletin/linux/111031-my-troubles-intel-i810-drivers-xorg-fixed.html
It uses an xorg.conf Monitor-Section Option statement that affects only adapters that support RandR 1.2 (The X Resize and Rotate Extension) and is apparently ignored by other adapters. The man-page definition of it is:
Quote:
Option PreferredMode string
This optional entry specifies a mode to be marked as the preferred initial mode of the monitor. (RandR 1.2-supporting drivers only)

I have tried this Option using the same resolution as in the Screen Section and, indeed, the problem is corrected. I have modified /usr/sbin/xorgwizard to generate the Option statement with the same value as that placed in the Screen Section "Modes" statement. I have also tested the fix on other PCs (that don't need it) and there is no impact.

Anyone can try this out by extracting the wizard to someplace easily accessible from the command prompt. Boot with pfix=nox, mount the location of the new xorgwizard file, then run it using the full path name. Then run xwin to finish bootup.

If already booted to the desktop, just exit to the command prompt, find and run the wizard as above, then xwin.
Richard

It's done. Thanks for that, especially the difference file so I was able to see quickly what you did._________________http://bkhome.org/news/

The new pwget tool directs the user to "cut" out a web address and paste it, while all that is needed is to "copy" the URL to paste it. Pwget's instructions can be made more precise by the replacement of "Cut" with "Copy" in statements 12 and 29 of the script in /usr/local/Pwget.

While verifying my minor changes to pwget with xfdiff, I discovered that my change on line 29 was not indicated. The same change on line 12 at character 16 of a ~130-char line was detected.
...
Since xfdiff did not find the word or indicate the maximum line length it compares, its credibility is dubious. It cannot be trusted.

Hmmm. Perhaps you could send an email to the author of xfdiff.
I sent him an email about 6 months ago informing of the patch-file-generation just crashing. No response. However, I did contact him once before that, with another difficulty and he did reply on that occasion. It has been a long time since he upgraded xfdiff, so he should be gently persuaded to do so._________________http://bkhome.org/news/

While testing my xorgwiz fix at the command line before running xwin, I changed the current directory to my flash drive. After executing xwin and getting back to the desktop, I found that the "file" icon and ROX menu entry resulted in display of the contents of the flash drive, instead of the familiar /root directory. Other programs exhibit the same default directory. Apparently the "$@" parameter in the underlying scripts relies on the setting of the "current directory".

Unless this is an intended "feature," it can be remedied by having xwin ensure that the current directory is "~/". The following statement would accomplish that, inserted after line 9 of xwin for both 3.97 and 3.02, and similarly for other Puppy versions.

Code:

cd ~/ #v3.98 Ensure current directory is root, in case changed at command prompt, so rox icon and menu item open only at home directory. rerwin

Richard

Yes, I can't think of any reason why we would want that as a feature, so I have implemented your change._________________http://bkhome.org/news/

OFF TOPIC
I'm surprised these incremental versions aren't being additionally offered via Xdelta patches (as opposed to only full-size ISOs), to really reduce the download time for the majority of users, who'll already have a previous alpha.

I saw your earlier posts about xdelta, but I just never got round to looking at it. Just now looked a the link -- looks good. Perhaps I will use it for the next Dingo, hopefully the beta._________________http://bkhome.org/news/

'I checked /etc/ppp/chap-secrets in 301 and found it contained the literal username and password separated by a 3 character sequence (tab, asterix and tab) followed by a blank line' pap-secrets is identicle.

Thanks for including cdp. It's ideal for older CD drives with an external headphone socket or where the PC was built with the luxury of a CD drive to sound card cable - oh the expence!

***Edited to make hyperlink out of plain url.Last edited by zygo on Mon 10 Mar 2008, 18:47; edited 1 time in total

I have a new PC with vista on a SATA drive which I need for another project. It has 2GB of RAM and I want to use it with Puppy live-cd on a regular basis. I have mistakenly booted Puppy without pfix=ram and when I next booted vista it complained then 'fixed' the disk. Will changing the first line in isolinux.cfg to 'default puppy pfix=ram' avoid this?

What I would really like is a way to stop Puppy scanning the IDE bus at boot or any other time. Or just sata drives. Or maybe all drives including usb. Is there an easy way to do one of these like delete a module before remastering? I'd like the drive to disappear under Linux. The trouble is ms has to keep changing ntfs to disuade the use of alternative OSs. And that although I have a backup, that doesn't mean the cost of recovery is zero.

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