SolidPup 5.1.1-B Lite and OBXF
Wbar coverup
If you just want Wbar (and/or Tint2) to no be covered up by open windows .... just set the margins in Openbox configuration Manager - Margins ... to leave these areas uncovered. Top-58, bottom-32 works well on my screen. You can still move windows to the edges of the screen but they should no automatically maximize to cover those areas.
In IceWM (my favorite), I do not think there is a way to insure Wbar remains uncovered.
I have been using Solid pup 5.1.1-B rc2 a lot lately and I like it. Only problem I have had is that sometime it locks-up on an X restart, shutdown, or reboot when I am running IceWM. Seems random but may be related to some prior activity during that session ..... more testing needed. So Far, no lock-ups while using Openbox. Thanks ... KJ
In IceWM (my favorite), I do not think there is a way to insure Wbar remains uncovered.
I have been using Solid pup 5.1.1-B rc2 a lot lately and I like it. Only problem I have had is that sometime it locks-up on an X restart, shutdown, or reboot when I am running IceWM. Seems random but may be related to some prior activity during that session ..... more testing needed. So Far, no lock-ups while using Openbox. Thanks ... KJ
Re: Wbar coverup
Hmmm, that gives me an idea. I could get a widescreen monitor and reserve the right hand margin and put the wbar there vertically. (then the windows will be over at top left where I like them, but wbar will still be visible). I never really liked widescreen - but maybe that would be a good way to use one.KJ wrote:just set the margins in Openbox configuration Manager - Margins ... to leave these areas uncovered. Top-58, bottom-32 works well on my screen. You can still move windows to the edges of the screen but they should no automatically maximize to cover those areas.
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
Re: Solidpup 5.1.1 final
Hi, recently I had seen something on this forum that Solidpup was to be a kind-of simplified Puppy, and thought to put it on my friend's new (old) computer, a Dell Latitude D610.Tman wrote:I've decided to get back on the saddle and work on another puplet..well not a brand new one.
I felt that I had left SolidPup sort-of unfinished, so I decided to work on it some more.
This will probably be the final release for version 5.1.1. It should be ready in a couple weeks. There will be a lot of changes.
All she does is internet email (Yahoo) and Web browsing, and uses the Opera browser.
But I've run into a problem, which I think Pemasu mentioned somewhere in this forum: when I click on shutdown and choose the restart X, the computer seems to do nothing, with a dark screen.
After a while, all I can do is power off.
Thanks,
Sheldon
Re: Solidpup 5.1.1 final
KJ: The only problem with your idea with Openbox margins is that it reduces screen real-estate.
I would rather just use the toggle ShowDesktop function, but thanks for the suggestion.
Try setting up a savefile with Pupsaveconfig then reboot the computer.
The machine may go black for a while, as it creates a savefile before the reboot, but hopefully, it will work for you.
I have no solution for the black screen. Maybe Pemasu or someone else will have the needed info.
By coincidence. I have made a patch for Solidpup511-B Lite rc2 with bug fixes.
The pet also contains modifed restarwm, wmpoweroff, and wmrestart scripts...these are needed for use with "openbox + xfce4-panel"
I will be posting the patch shortly.
-
I would rather just use the toggle ShowDesktop function, but thanks for the suggestion.
Hmmm, I've never encountered that problem, but I think it might do something with certain video drivers.sheldonisaac wrote: Hi, recently I had seen something on this forum that Solidpup was to be a kind-of simplified Puppy, and thought to put it on my friend's new (old) computer, a Dell Latitude D610.
All she does is internet email (Yahoo) and Web browsing, and uses the Opera browser.
But I've run into a problem, which I think Pemasu mentioned somewhere in this forum: when I click on shutdown and choose the restart X, the computer seems to do nothing, with a dark screen.
After a while, all I can do is power off.
Thanks,
Sheldon
Try setting up a savefile with Pupsaveconfig then reboot the computer.
The machine may go black for a while, as it creates a savefile before the reboot, but hopefully, it will work for you.
I have no solution for the black screen. Maybe Pemasu or someone else will have the needed info.
By coincidence. I have made a patch for Solidpup511-B Lite rc2 with bug fixes.
The pet also contains modifed restarwm, wmpoweroff, and wmrestart scripts...these are needed for use with "openbox + xfce4-panel"
I will be posting the patch shortly.
-
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
Re: Solidpup 5.1.1 final
Thanks, Tman. That was a fast reply!Tman wrote:Hmmm, I've never encountered that problem, but I think it might do something with certain video drivers.
Try setting up a savefile with Pupsaveconfig then reboot the computer.
The machine may go black for a while, as it creates a savefile before the reboot, but hopefully, it will work for you.
I have no solution for the black screen. Maybe Pemasu or someone else will have the needed info.
I am trying that on my own Dell D610.
Thus far I have a new warysave-oct29.2fs in the /mnt/home/solid/ directory.
Rebooted OK.
Then I copied it to /mnt/home/pristine-warysave-oct29.2fs
Rebooted OK.
I'm fairly sure it's 1024x768 24-color. Where do I look to check that?
Now I'll try Shutdown -> Restart X
Good! Back to the desktop!
Now what about Restart WM ..
AH! Good!! Also worked!
THANK YOU!!
I'll be back later with questions on simplifying the desktop even more for her.
Thanks again,
Sheldon
Re: Solidpup 5.1.1 final
From the console, type:xorgwizard and you'll find the settings in there...sheldonisaac wrote: I'm fairly sure it's 1024x768 24-color. Where do I look to check that?
it won't help if you're screen is black in the console though.
But you would get the same startup screen if you booted without a savefile, or in "pfix=ram" mode.
I have created a patch for Solidpup-511-Lite-rc2.
Also, I have made an xfce4-panel pet available for testing.
For the xfce4-panel to work you need to install all of the pets linked below:
0) solid511B_Lite_rc2_patch-1.pet (not necessary for solidpups newer than 511-B-rc2)
1) dbus-1.2.4.2permissive-1-w5.pet
2) dbus_glib-0.88-solid511B.pet
3) libwnck-2.30.7-solid511B.pet
4) xfce4panel_FULL-4.10-solid511B.pet
5) REBOOT the computer...needed for the newly installed dbus and dbus-glib to work.
If you want to get tint2 panel back, you need to manually edit the file named: /etc/openbox_panel ... change xfce4-panel to tint2 (no spaces) and restart-x.
An automated system for this is in the works.
The great thing about this panel is that you can drag and drop items from the menu to the panel (taskbar) or from the menu to the desktop.
-
Also, I have made an xfce4-panel pet available for testing.
For the xfce4-panel to work you need to install all of the pets linked below:
0) solid511B_Lite_rc2_patch-1.pet (not necessary for solidpups newer than 511-B-rc2)
1) dbus-1.2.4.2permissive-1-w5.pet
2) dbus_glib-0.88-solid511B.pet
3) libwnck-2.30.7-solid511B.pet
4) xfce4panel_FULL-4.10-solid511B.pet
5) REBOOT the computer...needed for the newly installed dbus and dbus-glib to work.
If you want to get tint2 panel back, you need to manually edit the file named: /etc/openbox_panel ... change xfce4-panel to tint2 (no spaces) and restart-x.
An automated system for this is in the works.
The great thing about this panel is that you can drag and drop items from the menu to the panel (taskbar) or from the menu to the desktop.
-
hum, at this time, don't work for me.Tman wrote:I have created a patch for Solidpup-511-Lite-rc2.
Also, I have made an xfce4-panel pet available for testing.
For the xfce4-panel to work you need to install all of the pets linked below:
0) solid511B_Lite_rc2_patch-1.pet (not necessary for solidpups newer than 511-B-rc2)
1) dbus-1.2.4.2permissive-1-w5.pet
2) dbus_glib-0.88-solid511B.pet
3) libwnck-2.30.7-solid511B.pet
4) xfce4panel_FULL-4.10-solid511B.pet
5) REBOOT the computer...needed for the newly installed dbus and dbus-glib to work.
If you want to get tint2 panel back, you need to manually edit the file named: /etc/openbox_panel ... change xfce4-panel to tint2 (no spaces) and restart-x.
An automated system for this is in the works.
The great thing about this panel is that you can drag and drop items from the menu to the panel (taskbar) or from the menu to the desktop.
-
I didn't find the /etc/openbox_panel file, so I created it ?
but no, don't work.
later, sure !
You need to install all of the pets in the list.Arefacti wrote: I didn't find the /etc/openbox_panel file, so I created it ?
but no, don't work.
later, sure !
Disregard message to restart-x, but after installing all of the pets, reboot the computer.
If it still doesn't work, don't worry...I will put out a pup that comes with it preinstalled.
EDIT: oh, and if you are in icewm, you need to switch to Openbox. This can be done easily by using WM Switcher.
typing restartwm openbox from the terminal will also work.
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
Sorry, what is the patch supposed to do?Tman wrote:I have created a patch for Solidpup-511-Lite-rc2.
Also, I have made an xfce4-panel pet available for testing.
For the xfce4-panel to work you need to install all of the pets linked below:
0) solid511B_Lite_rc2_patch-1.pet (not necessary for solidpups newer than 511-B-rc2)
-
Below is my specs; do I need the patch? Thanks
=== Distro Specifications ===
Operating System: SolidPup 511
Desktop Panel: tint2 version 0.9rc1
Desktop Window Manager: Openbox 3.4.11
Desktop Start: xwin openbox
=== /etc/DISTRO_SPECS ===
#One or more words that identify this distribution:
DISTRO_NAME='SolidPup'
#A three-digit numeric value, version number of this distribution:
DISTRO_VERSION=511
#A two-digit numeric value, minor-version number of this distribution:
DISTRO_MINOR_VERSION=00
#The distro whose binary packages were used to build this distribution:
DISTRO_BINARY_COMPAT='puppy'
#Prefix for some filenames: exs: qrkysave.2fs, qrky-141.sfs
DISTRO_FILE_PREFIX='wary'
#The version of the distro whose binary packages were used to build this distro:
DISTRO_COMPAT_VERSION='wary5'
#the kernel pet package used:
DISTRO_KERNEL_PET='linux_kernel-2.6.32.28-2-w5.pet'
#16-byte alpha-numeric ID-string appended to vmlinuz, wary_511.sfs, zw511228.sfs and devx.sfs:
DISTRO_IDSTRING='w511110528171105'
#Puppy default filenames...
#Note, the 'SFS' files below are what the 'init' script in initrd.gz searches for,
#for the partition, path and actual files loaded, see PUPSFS and ZDRV in /etc/rc.d/PUPSTATE
DISTRO_PUPPYSFS='wary_511.sfs'
DISTRO_ZDRVSFS='zw511228.sfs'
Hi Sheldon,
The patch contains some bug fixes, and hacked scripts.
It mainly has fixes for wbar, and hacked restartwm, wmreboot, and wmpoweroff scripts necessary for xfce4-panel.
So, in short..if you don't want to install the xfce4-panel to run with openbox, then you don't really need the patch.
Also I am uploading a Solidpup OBXF version.
OBXF is just short for "Openbox-xfce4panel". This is mainly to test the new desktop envrionment for bugs.
Along with the files needed to run xfce4-panel, I have only added Opera as an additional app, so far.
More apps will be added later on...
Please don't try to download the new OBXF pup yet... current upload time remaining is about 1hour from now.
The patch contains some bug fixes, and hacked scripts.
It mainly has fixes for wbar, and hacked restartwm, wmreboot, and wmpoweroff scripts necessary for xfce4-panel.
So, in short..if you don't want to install the xfce4-panel to run with openbox, then you don't really need the patch.
Also I am uploading a Solidpup OBXF version.
OBXF is just short for "Openbox-xfce4panel". This is mainly to test the new desktop envrionment for bugs.
Along with the files needed to run xfce4-panel, I have only added Opera as an additional app, so far.
More apps will be added later on...
Please don't try to download the new OBXF pup yet... current upload time remaining is about 1hour from now.
YES Tman !
It works !
very ergonomic !
Thannnnnnnnnnnnnks !
I want too put a screen capture but don't know how, I look too
Edit :
Uploaded with ImageShack.us
Very sorry for the great pic, when I'll find how I must do to make good, I'll do
In fact, my problem was I have not the /etc/openbox_panel file.
So, I did a symlink /usr/bin/xfce4-panel in the /root/Startup directory (and remove the symlink wmbar in).
It works !
very ergonomic !
Thannnnnnnnnnnnnks !
I want too put a screen capture but don't know how, I look too
Edit :
Uploaded with ImageShack.us
Very sorry for the great pic, when I'll find how I must do to make good, I'll do
In fact, my problem was I have not the /etc/openbox_panel file.
So, I did a symlink /usr/bin/xfce4-panel in the /root/Startup directory (and remove the symlink wmbar in).
It sounds like you didn't install the patch first, because the patch also removes that symlink to wbar and replaces it with "wbar_launcher".Arefacti wrote: In fact, my problem was I have not the /etc/openbox_panel file.
So, I did a symlink /usr/bin/xfce4-panel in the /root/Startup directory (and remove the symlink wmbar in).
When xfce4-panel is running, the wrapper doesn't run wbar...but wbar will launch by itself in icewm. I recommend installing the patch now... the desktop will revert back to openbox + tint2 once you restart-x.
Next enter this in the terminal:
Code: Select all
geany /etc/openbox_panel
Of course, fbpanel is not installed by default, so it will only work after you install it. fbpanel-6.0-patched-3-q1.pet
I have just found a rather odd problem with Opera... .pet files downloaded as .gz files. Does anyone know the solution for this???
> I have just found a rather odd problem with Opera... .pet files downloaded as .gz files. Does anyone know the solution for this???
Yep. Simply rename them with a *.pet suffix when you save them. Will unpack and install stuff as usual.
Probably opera derives its suffix from the first few bytes of the file instead of the filename itself. (And indeed pet files do use the .gz compression.)
BFN.
Yep. Simply rename them with a *.pet suffix when you save them. Will unpack and install stuff as usual.
Probably opera derives its suffix from the first few bytes of the file instead of the filename itself. (And indeed pet files do use the .gz compression.)
BFN.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
I see you are using Zimbra. What do you think of it? I am looking for a new email interface. My Fastmail webmail has changed format and I don't like it.Arefacti wrote:Uploaded with ImageShack.us
not bad, good functions, reactive, 10 Go, but just a little bit uglygreengeek wrote:I see you are using Zimbra. What do you think of it? I am looking for a new email interface. My Fastmail webmail has changed format and I don't like it.Arefacti wrote:Uploaded with ImageShack.us
Musher, thanks for the tip. It kinda makes sense since .pet files are just .gz files with the extension renamed.
This problem doesn't happen to me all the time in Opera. I've downloaded a lot of pets that have not been renamed to .gz files.
... strange indeed.
I have some bad news... bad news for me at least. I said in some previous post that Shinobar's getnvidia pet did not work for me.
So I finally got around to try and make the nvidia pet manually. Unfortunately, that didn't work for me either.
The nvidia-installer.log file says this:
I couldn't figure out the problem with that info though.
As a hunch, I loaded up an older version of Solidpup, and tried Shinobar's getnvidia.pet. It worked perfectly for me.
If I can't figure it out the problem, then it looks like I will have to backtrack to version beta-2.3, and start again from there... aargh!
Luckily, I documented (almost) all of the changes I made along the way, but I estimate that this will set me back about 2 weeks.
Current releases are still stable to use, but having video drivers not being able to compile is an absolute no-no for me.
In the meantime, you guys can play with what I've released and a new Nvidia pet is now available for testing. nvidia-glx-304-60-k2.6.32.28.pet
-
This problem doesn't happen to me all the time in Opera. I've downloaded a lot of pets that have not been renamed to .gz files.
... strange indeed.
I have some bad news... bad news for me at least. I said in some previous post that Shinobar's getnvidia pet did not work for me.
So I finally got around to try and make the nvidia pet manually. Unfortunately, that didn't work for me either.
The nvidia-installer.log file says this:
Code: Select all
nvidia-installer log file '/var/log/nvidia-installer.log'
creation time: Thu Nov 1 10:39:17 2012
installer version: 304.60
PATH: /bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/X11R7/bin:/root/my-applications/bin:/usr/games
nvidia-installer command line:
./nvidia-installer
Using: nvidia-installer ncurses user interface
-> License accepted.
-> Installing NVIDIA driver version 304.60.
-> Performing CC sanity check with CC="cc".
-> Performing CC version check with CC="cc".
-> Kernel source path: '/lib/modules/2.6.32.28/source'
-> Kernel output path: '/lib/modules/2.6.32.28/build'
-> Performing rivafb check.
-> Performing nvidiafb check.
-> Performing Xen check.
-> Cleaning kernel module build directory.
executing: 'cd ./kernel; make clean'...
-> Building kernel module:
executing: 'cd ./kernel; make module SYSSRC=/lib/modules/2.6.32.28/source SYSOUT=/lib/modules/2.6.32.28/build'...
NVIDIA: calling KBUILD...
make -C /lib/modules/2.6.32.28/build \
KBUILD_SRC=/usr/src/linux-2.6.32.28 \
KBUILD_EXTMOD="/tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel" -f /usr/src/linux-2.6.32.28/Makefile \
modules
test -e include/linux/autoconf.h -a -e include/config/auto.conf || ( \
echo; \
echo " ERROR: Kernel configuration is invalid."; \
echo " include/linux/autoconf.h or include/config/auto.conf are missing."; \
echo " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo; \
/bin/false)
mkdir -p /tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel/.tmp_versions ; rm -f /tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel/.tmp_versions/*
make -f /usr/src/linux-2.6.32.28/scripts/Makefile.build obj=/tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel
cc -Wp,-MD,/tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel/.nv.o.d -nostdinc -isystem ./include -Iinclude -Iinclude2 -I/usr/src/linux-2.6.32.28/include -I/usr/src/linux-2.6.32.28/arch/x86/include -include include/linux/autoconf.h -I/tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -Os -m32 -msoft-float -mregparm=3 -freg-struct-return -mpreferred-stack-boundary=2 -march=i486 -mtune=generic -Wa,-mtune=generic32 -ffreestanding -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -fno-stack-protector -fomit-frame-pointer -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -I/tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel -Wall -MD -Wsign-compare -Wno-cast-qual -Wno-error -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"304.60\" -Wno-unused-function -Wuninitialized -UDEBUG -U_DEBUG -DNDEBUG -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(nv)" -D"KBUILD_MODNAME=KBUILD_STR(nvidia)" -c -o /tmp/selfgz29675/NVIDIA-Linux-
x86-304.60/kernel/.tmp_nv.o /tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel/nv.c
In file included from /tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel/nv.c:12:
/tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel/os-interface.h:27:20: error: stdarg.h: No such file or directory
In file included from /tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel/nv.c:12:
/tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel/os-interface.h:87: error: expected declaration specifiers or '...' before 'va_list'
In file included from /tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel/nv-linux.h:14,
from /tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel/nv.c:13:
/tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel/nv.h:570: error: expected declaration specifiers or '...' before 'va_list'
In file included from ./include/linux/sched.h:54,
from ./include/linux/utsname.h:35,
from /tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel/nv-linux.h:40,
from /tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel/nv.c:13:
./include/linux/kernel.h:183: error: expected declaration specifiers or '...' before 'va_list'
./include/linux/kernel.h:187: error: expected declaration specifiers or '...' before 'va_list'
./include/linux/kernel.h:191: error: expected declaration specifiers or '...' before 'va_list'
./include/linux/kernel.h:195: error: expected declaration specifiers or '...' before 'va_list'
./include/linux/kernel.h:199: error: expected declaration specifiers or '...' before 'va_list'
./include/linux/kernel.h:239: error: expected declaration specifiers or '...' before 'va_list'
./include/linux/kernel.h:535: error: expected declaration specifiers or '...' before 'va_list'
In file included from ./include/linux/sched.h:91,
from ./include/linux/utsname.h:35,
from /tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel/nv-linux.h:40,
from /tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel/nv.c:13:
./include/linux/kobject.h:77: error: expected declaration specifiers or '...' before 'va_list'
In file included from ./include/linux/cpufreq.h:17,
from /tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel/nv-linux.h:93,
from /tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel/nv.c:13:
./include/linux/device.h:531: error: expected declaration specifiers or '...' before 'va_list'
In file included from ./include/acpi/acpi.h:63,
from /tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel/nv-linux.h:276,
from /tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel/nv.c:13:
./include/acpi/acpiosxf.h:261: error: expected declaration specifiers or '...' before 'va_list'
/tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel/nv.c:3725: error: expected declaration specifiers or '...' before 'va_list'
make[4]: *** [/tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel/nv.o] Error 1
make[3]: *** [_module_/tmp/selfgz29675/NVIDIA-Linux-x86-304.60/kernel] Error 2
make[2]: *** [sub-make] Error 2
NVIDIA: left KBUILD.
nvidia.ko failed to build!
make[1]: *** [module] Error 1
make: *** [module] Error 2
-> Error.
ERROR: Unable to build the NVIDIA kernel module.
ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for details. You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com.
As a hunch, I loaded up an older version of Solidpup, and tried Shinobar's getnvidia.pet. It worked perfectly for me.
If I can't figure it out the problem, then it looks like I will have to backtrack to version beta-2.3, and start again from there... aargh!
Luckily, I documented (almost) all of the changes I made along the way, but I estimate that this will set me back about 2 weeks.
Current releases are still stable to use, but having video drivers not being able to compile is an absolute no-no for me.
In the meantime, you guys can play with what I've released and a new Nvidia pet is now available for testing. nvidia-glx-304-60-k2.6.32.28.pet
-
Last edited by Tman on Fri 02 Nov 2012, 18:53, edited 2 times in total.
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
In Opera 12.02:Tman wrote:Musher, thanks for the tip. It kinda makes sense since .pet files are just .gz files with the extension renamed.
This problem doesn't happen to me all the time in Opera. I've downloaded a lot of pets that have not been renamed to .gz files.
... strange indeed.
Tools->Preferences->Advanced->Downloads
Uncheck "File types opened with Opera"
Edit the MIME type application/x-gzip
by adding pet to the comma-separated list of File extensions
--------
EDIT: I'm not sure about that. I do recall seeing something (perhaps in an Opera thread or another forum) about hopw to fix that problem.
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
Re: Solidpup
Hi, how can I have it connect to wireless on bootup?
I'd put a script in /root/Startup if I knew what it should say, or in /etc/rc.d/rc.local?
I'd been using WEP, but this Dell Latitude D610 seems able to do WPA-2
Network Wizard lets me connect, but it doesn't connect on later boot,
Thanks,
Sheldon
I'd put a script in /root/Startup if I knew what it should say, or in /etc/rc.d/rc.local?
I'd been using WEP, but this Dell Latitude D610 seems able to do WPA-2
Network Wizard lets me connect, but it doesn't connect on later boot,
Thanks,
Sheldon