Quickset Puppy

[shinobar]

It automatically starts up the desktop with 800x600 screen size, Universal timezone, us-English keyboards.
You can change the first setup with one window.
The network connection is also automatic in case an eth0 interface is found and DHCP is available(net-setup update required).

Quick setup Puppy is easy to make up based on any Puppy v4.x(do not apply on Puppy-5.x).
Download quicksetup-1.1-p4-xvesa.pet (UPDATE: 1 Dec 2010)from here.
Follow the document.

This technique can not apply to most of Puppy-5.x which do not have Xvesa.
To get direct desktop with Xorg version 1.7, refer Lucid Puppy Quickset edition(LupQ). You need to modify /usr/bin/xwin. See the post:
http://www.murga-linux.com/puppy/viewto ... 149#476149

Optional add-ons (all available from the same download link above)

• Net-setup update
• Remasterpup2 update
• Grub4Dos config
• Winfonts
• Frugal Installer
• rc_country-20101201.pet

Related topic:Add a Graphical Boot Menu to your Puppy Live CD

A good example is available in pup-431JPqs3.iso found here.it is initially japanese but you can change the settings with one window dialog.


(outdated)
firstsetup-0.9en.pet (14 March 2010)]from here.
Follow the document.

[Puppyt]

shinobar, I thank you and your Puppy Linux Japanese Team very much for your work here with Quickset.

I look forward to giving you feedback on this very interesting offering - automatic eth0 connection is just what I was after, and in your Quickset liveCD version a very welcome approach to non-wireless mobile computing. This is very much appreciated.

[big_bass]

shinobar

a very needed GUI

nice and clean and easy to read

great work
and a bonus ! ethernet set up

Joe

[davesurrey]

shinobar
I agree with big_bass. Thank you for this and also frugalinstaller, pupsaveconfig and Grub4dosconfig. They are all very useful and needed apps IMO.
I also just tried the pup431JPqs0 and found it shows off these apps really well.
I hope more people here see your good work.

Thanks again
Dave

[sc0ttman]

shinobar
I agree with big_bass. Thank you for this and also frugalinstaller, pupsaveconfig and Grub4dosconfig. They are all very useful and needed apps IMO.
I also just tried the pup431JPqs0 and found it shows off these apps really well.
I hope more people here see your good work.

Thanks again
Dave

Agreed.. Your work is great.. I look forward to playing with it more!

[puppymartin]

Very Good!
I will use this in the next Browserlinux.
One thing: us@(USA/univarsal) -> us@(USA/universal)

[shinobar]

Now firstsetup updated to firstsetup-0.9en.pet. See the top of this topic.
Recommended to use with next add-ons(not included in this package anymore).
* Net-setup update
* Remasterpup2 update
* Grub4Dos config

[shinobar]

Uploaded quicksetup-1.0-p4-xvesa.pet for Puppy-4.x.
See the top post of this topic.

[sc0ttman]

Uploaded quicksetup-1.0-p4-xvesa.pet for Puppy-4.x.
See the top post of this topic.

yeeeeaaaaahh.... Good man shinobar!

Gonna play with that as soon as I get home from work!

EDIT: had trouble with this.. I sent you a PM about it, hope you don't mind

EDIT EDIT: I finally got past the problem of booting to Xvesa, without messing up Xorg in 4.2..
That works...

But quicksetup-1.0-p4-xvesa.pet has caused a new problem:

Main language settings are not remembered.. even using the old locale tool..

And now I get errors in the terminal for many apps, usually ROX..
It says

Code: Select all

Gtk-WARNING **: Locale not supported by C Library
Using fallback C locale.

Then, the pmount script will not work, because yaf-splash seems to die, complaining about unsupported locales...

However, pmount works fine before the "personalize settings 1.3d" gui has finished, but once it sets some options, then pmount will not work..

If anyone can help me that would be lovely, if not.. OK!

[shinobar]

And now I get errors in the terminal for many apps, usually ROX..
It says

Code: Select all

Gtk-WARNING **: Locale not supported by C Library
Using fallback C locale.

On the virtual terminal, type:

Code: Select all

locale

Most of old Puppy's are lacking UTF-8 support on the virtual terminal even the urxvt is compiled with UTF-8 support.

EDIT: Attached UTF-8 support for Puppy-4.x.
Use with the quicksetup-1.0-p4-xvesa.pet.
And the urxvt should have UTF-8 support.

[shinobar]

I finally got past the problem of booting to Xvesa, without messing up Xorg in 4.2..

As for the Xorg on Puppy-4.x, I remember the BrowserLinux does the direct to the desktop. It uses vesa driver of Xorg, but i am not sure where is trap.
puppymartin must know.

[sc0ttman]

I finally got past the problem of booting to Xvesa, without messing up Xorg in 4.2..

As for the Xorg on Puppy-4.x, I remember the BrowserLinux does the direct to the desktop. It uses vesa driver of Xorg, but i am not sure where is trap.
puppymartin must know.

Thanks a lot for all your packages and help.. You're a star.. I'm gonna try to get this all working without bothering you again! I know you're busy enough!

[shinobar]

I'm gonna try to get this all working without bothering you again! I know you're busy enough!

Thanks sc0ttman. Don't hesitate. I am willing to see your try and progress on this topic.

[sc0ttman]

I'm gonna try to get this all working without bothering you again! I know you're busy enough!

Thanks sc0ttman. Don't hesitate. I am willing to see your try and progress on this topic.

OK then...

I'm using quicksetup1.0, in a custom 4.2 system...

I would be interested to know if my problems are present on a normal 4.2..

(Because what I am using is based on TurboPup/PA9 but I don't think TurboPup has special locale settings or functions..)

Here is my current situation:

1. The firstrun dialog does not change the main language (LANG set in /etc/profile) but all other options work fine.

After firstrun, doing the 'locale' command in the terminal always returns en_US (no change).

Running firstrun from the terminal shows this error (maybe relevant, maybe not):

Code: Select all

/usr/bin/firstrun: line 206: locale_name: command not found

2. When I use the old 'chooselocale' tool to change locale, then I get when running other apps:

Code: Select all

Gtk-WARNING **: Locale not supported by C Library
Using fallback C locale.

After I get this message, pmount will not work.

I have not yet installed your utf-8 pet file, but I have edited it and made a new package.

I have added symlinks in '/usr/X11R7/lib/X11/locale/'. Example: am_ET.UTF-8 --> am_ET.utf8

(After reading /usr/bin/firstrun I think the symlinks will be required, but I am not sure...)

[sc0ttman]

OK.. update:

I have installed your utf-8 package, with my added symlinks and remastered.
I booted the new version, and firstrun loads, so I set the locale to en_GB at first boot.

Firstrun detects the change and applies it successfully
I then run 'locale' in the terminal and get en_GB..

So it works on first boot (even when I switch to Xorg )
However, it is not perfect yet.

1. The change of locale is not shown next time I run firstrun.
Also it will not detect or apply any more changes I make to the locale.
Example:

- It always shows en_US, every time.
- If I change only the locale, I get 'Nothing is changed'.
- If I change locale and keyboard, I get only 'Changes completed: (Keyboard)'

2. If I do not change from Xvesa to Xorg (or vice versa), the colour-depth will not change.
Example: I cannot change from Xvesa 16bit to Xvesa 24bit.

3. The old chooselocale tool still messes things up (locale command returns '**: not found').

4. Pmount works fine before I use firstrun. It works after firstrun, but only when I type 'pmount' into rxvt or sakura.

After firstrun, when I run pmount from jwm menu(s) it does not work.
I even tried it when the jwm menu entry is 'rxvt -e pmount' - didn't work.

(NOTE: pmount fails through jwm menus, even when 'locale' returns 'en_US', but only after firstrun.. I'm using your jwm i18n)

[shinobar]

Hi, sc0ttman.

Code: Select all

/usr/bin/firstrun: line 206: locale_name: command not found

It is a bug, but not serious.
Color depth maybe a bug. I can hopefully fix.

Locale issue: humm... not easy.
Basically, Puppy-4.2x does not support unicode,utf8/UTF-8.
Its native support is only English. Others are downloaded from the net.
But excepting some Europeans, they require unicode. So the locale support of the Puppy-4.2x is halfway.

English locales should work. And some European may work.
I tried test, but unfortunately, Puppy-4.2.1 is unstable with my hardware, may be the graphic driver does not fit with my NVIDIA 8800GTX.

[sc0ttman]

Thanks for the reply...

my problems in summary:

1. firstrun works perfect first time
2. but locale changes not detected or applied after that
3. colour depth change requires change in X server
4. pmount still fails after firstun is used (except from terminal)


I do not need all of these fixed. But I would like:

1. Firstrun to show correct locale after it is changed from en_US
2. Firstrun to allow change of colour depth, without change of X server

I will try to do this myself, but I may find myself back here!

[shinobar]

Found bugs with xvesa support on the last version.
And the last version did not support Puppy4.2x.

Try quicksetup-1.1-p4-xvesa.pet. See the top of this topic.
Note the UTF-8 support on Puppy-4.2x is another issue.

[sc0ttman]

Found bugs with xvesa support on the last version.
And the last version did not support Puppy4.2x.

Try quicksetup-1.1-p4-xvesa.pet. See the top of this topic.
Note the UTF-8 support on Puppy-4.2x is another issue.

Hi shinobar, I installed quicketup-1.1 on a 4.2 system..

I also installed rc_country-20101201.pet

After remaster and reboot, I found no issues

The resolution and X server changes worked, straight to 24bit..
(I was not given the option to change 16 or 24bit first time)

Locale changes worked, and were remembered by firstrun, it always shows the correct locale now

The next time I ran it, from the 'Personalize Settings' menu item, I was also given the option of changing between 16 and 24bit

I changed only this option and the change was detected and applied correctly.

So, in summary, all changes worked, and all changes were detected the next time I ran firstun.

Good work

1 question though, what exactly does the new rc_country-20101201.pet file fix?

[shinobar]

After remaster and reboot, I found no issues

Thanks for the test. I am glad to hear that.

what exactly does the new rc_country-20101201.pet file fix?

The rc_country-20101201 is not essencial for this case.
It supports 3 things:

1. Allows both '*.UTF-8' and '*.utf8' for the locale name. ...But Puppy-4.2x basically does not support UTF-8.
2. Use /usr/sbin/keymap-set contained in the quicksetup or the 'Personalize settings', supports jp(Japanese) and br(Brasilian) keyboards.
3. Asks only the keymap when booted with 'pfix=nox'... works with the modified /etc/profile contained in the quicksetup. But i am not sure it was implemented.