Puppy Linux Discussion Forum

[Aitch]

Aw shucks, Joe
I just had my first fail to load.....
My new toy, an Edubook, [1Ghz 586 compatible/512Mb ram] won't load Slaxer_Pup
Gets so far, then can't find the Pupfiles on the external usb DVDR
I think it's because the usb drivers don't load early enough
ttuuxxx's 214X is the same, though TurboPup, Pupeee4.2, and 4.3 with 2.6.30.5 kernel all load successfully, though the video driver seems twitchy at 1280x600@60hz, - D1010 VGA and the network isn't recognised - RDC PCI5.sys in windoze
It does have an RT73 wifi card in, but my wireless is blocked, as I have broadband

Any thoughts?

Aitch

[pakt]

[pakt]

That brings me to a request.

I wonder if Joe could take up the challenge to compile the video and wireless drivers for the Edubook. These are the only drivers I've found:

http://www.deviceonchip.com/index.php?option=com_rokdownloads&view=folder&Itemid=27&id=13:vga
http://www.deviceonchip.com/index.php?option=com_rokdownloads&view=folder&Itemid=27&id=14:wireless

I can't remember how to get sound or the LAN working. I think sound was some kind of patch and LAN was supported in the newer kernels.

[big_bass]

Hey Paul (pakt)

I will be able to take a look at that in a few days

thanks for posting links for the sources

hope all is well with you

-----------------------------------------------------
I am finished with a Xdialog version of the slackware package tools
but testing still

I had to do a complete re write of some sections more then I originally planned to do
because of differences in dialog and xdialog
this was tricky to allow both
a xdialog and the original console package
tools to work together without conflicts

so best of both worlds in or out of X

I also added in some bonus things its looking good
trying to make the change over to using package tools
better in the X environment

heres a sneak peek at it
Joe

[Aitch]

Hi Paul, thanks

Joe

I just got sent a link to the manufacturer's site, which gives much more detail, by Jonathan, who I bought the Edubook from, and includes this quote,

[pakt]

[amigo]

That's the wording from the original pkgtool. Both simply lead to another window which lists all the packages in the CWD or all those installed and lety you choose which packages to operate on.

[pakt]

Hi amigo,

Does the menu have to follow the original wording? There's no way that the user can tell there are one or more windows that follow.

Might be a good opportunity here to correct the ambiguities

Paul

[big_bass]

Hey Paul (pakt)

Thanks for the suggestions

those are /were the official messages of pgktools
but I agree if they could be made clearer lets do it

I had to edit installpkg also to display xdialog
that shows more info of what is happening
I attached a screen shot


and I added in the menu your edited messages
heres a screen shot

if you poke inside of pkgtools you will see that it is
a complex multi function script a lot of checks are made to the packages

xdialog by default design is for static menus
but I figured out a work around to generate dynamic menus

for the remove packages and the view packages
the dialog version uses the up and down arrows and the spacebar
to control the selections

using Xdialog you have the mouse and slide bar instead
to control your selections which is more user friendly
when your not in the console


Joe

[big_bass]

pkgtoolsx
UPDATED 2-20-2010

moved to current page


ok here it is

Xdialog version of packagetools (pkgtools)

so now its an X environment tool !

you should have the my pkgtools-13.0-patched-10-i486-slxr.pet
already installed its safe to have both since no files get over written

one for console one for X

Tip:if you have your packages in another directory copy the
pkgtoolx script into that folder and run it from there the
default is root

fixed slack-desc typo
added in a bug fix update from the official package
changed $TMP and ADM_DIR back to the defaults
I hard linked them while writing the script
to track down problems with echoing vars
Joe

[amigo]

Joe, are they both against the slackware-13.0 version of pkgtools?

[big_bass]

Hey Gilbert (amigo)

yeah so if you diff them out you'll see the changes

only a small edit on the bottom of the script comment out
the fixmenus and the jwm restart you could remove
before testing on a "slackware" base besides that it should be fine

for the official tools pkgtools and installpkg were changed
the other scripts weren't modified
some new scripts get auto built in /var/log/setup/tmp

/var/log/setup/tmp/xremove_package_viewer
/var/log/setup/tmp/view_all_tgz
/var/log/setup/tmp/viewsrc2
/var/log/setup/tmp/xpackage_viewer
/var/log/setup/tmp/new_installer_list
/var/log/setup/tmp/list_of_installed_packages2
/var/log/setup/tmp/reply2




also I will only use tgz or txz
Joe

[Aitch]

Nice, Joe, thanks

Aitch

[amigo]

I looked at those last night for a while. I noticed a couple of things you might want/need to change. This:

[big_bass]

Hey Gilbert (amigo)

fixed slack-desc typo
added in a bug fix update from the official package
changed $TMP and ADM_DIR back to the defaults
I hard linked them while writing the script
to track down problems with echoing vars

because of the mishap with $TMP
is usually /tmp
and not /var/log/setup/tmp
as package tools uses

this will be a lot easier to read
but not clean just yet

thanks for the xz update
I must of had an earlier version without the bug fix
I didn't change that line of code

I know its a bit messy because of the parts I had to generate
the dynamic menus with xdialog using an echo which makes it
messy to read maybe after you'll find a better solution to doing that part keep me posted open to suggestions

this is still very alpha but it is working as expected
thanks for pointing out some of the errors

I updated the package again
pkgtoolsx-13.0-noarch-5.tgz
Joe