EXTRASFSLIST is correct. PREVUNIONRECORD and LASTUNIONRECORD look wrong since they include "my-apps.sfs" and "wx_cb.sfs", both of which are squashfs version 3, for use by puppy412 and puppy421.
They are also in /initrd/tmp/EXTRASFSS:

EZ4arabs, could you test this idea? Simply boot a fresh puppy (pfix=ram), Go into BootManager and blacklist martian_dev, "probe-ERASE" in pupdial, reboot. I would expect no modem to be detected. Then probe for the modem in pupdial. If this works, it will lead to an elegant solution to your problem. Thanks.
Richard

I had the same idea yesterday before reading your request and when I saw the result I was going to post it here but I said to myself rerwin will definitely" say what are you doing man,stop wasting my time? there is something wrong with your modem or you did something wrong."
here is what pupdial found:

I did blacklist martian and what you compiled was ltmodem so what martian core vars is doing there and does [VUART) stands for virtual uart?
it would be interesting to see what will happen if it was tried by Diamond in this thread:
http://www.murga-linux.com/puppy/viewtopic.php?search_id=1861976780&t=46613

finds file names that contain ONEBASE as a substring, as well as the one that is identical. This is a problem when you have two files with names like "xxxx.sfs" and "xxxx-sfs4.sfs". grep matches "xxxx.sfs" to the leading "xxxx-sfs" in "xxxx-sfs4.sfs", so "xxxx.sfs" gets written to "/tmp/EXTRASFSS" when it should not be.
The simple solution is to change the line to

Thanks for the advice on how to clean my mouse. Unfortunately that doesn't apply to my situation. The Dell Inspiron 8200 is a laptop - one of the older laptops that offer both a touchpad and and eraser-style pointer. Just for grins I did pull out a ps/2 external mouse, but that doesn't make any difference. The pointer still disappears every few minutes....

@hiveman,
I don't think this problem has any connection to mouse or touchpad. It sounds like the "invisible cursor" problem I've seen on a number of machines with shared video ram. The fix for that is to edit xorg.conf and uncomment the option for software cursor. I've been campaigning for a simple check box in xorgwizard, and some text to describe the problem, for some time. It doesn't always show up, even on the same model of machine, because it depends on the size and speed of the shared memory.

Like some other people with the EeePC I have also had problems with the audio mixer shown in the jwm tray on my ASUS EeePC 900A. I haven't described it before, because we were still dealing with more serious things, like fan control and possibly burning processors. I'll wait until 4.3.1 stabilizes before tackling this specialized problem.

The Xandros system which came installed is really slow, but it does have exactly the right mixer, with controls for both volume and microphone. The sound quality when using Skype and a headset with microphone is excellent. Under 4.3 I've never gotten the microphone adjusted properly, even after following posted advice about using alsamixer. If we could use that mixer supplied with the machine I would be happy. Anyone know how it works? I'm not familiar with Xandros, and ASUS has hidden a number of proprietary things on the EeePC.

Right now I'm on a Dell D610, with the Broadcom 5751 gigabit ethernet adapter for wired connections and the Intel 2915ABG adapter for wireless. 4.3, and the RCs for 4.3.1 work nicely here, with one real irritation: sometimes the network interfaces come up with the Broadcom as eth0 and the Intel as eth1, and sometimes they are the other way round. This causes the automatic wireless reconnection to fail even though it was set up correctly and nothing else has changed.

I'm guessing this is due to the order in which the modules load, not necessarily a problem with the networking wizard.

2. No compatible modules found by CPU Frequency Scaling Tool. Compatible modules are found for both systems under Puppy 430.

1. No ROX menu entry for Partview app (found button at left of panel). Note also that "free" figures returned by Partview do not agree with those returned by df command. Differences range between 10% and 45%. I also suggest Partview *not* employ "alert" color red.

Barry updated the wifi firmware in Puppy 4.3, and all Intel firmwares are now included.
For the 5000 series devices Puppy now contains both the older and newer firmwares:
iwlwifi-5000-1.ucode
and
iwlwifi-5000-2.ucode

@ tempestuous, it appears that we have a wifi hardware problem since puppy dingo4 on certain machines with inbuilt cards.
In my own case a Toshiba Portege, no builds since the dingo release will connect from boot after initial pupsave. I have to switch the modem off then on before the system sees it, then i can search for an available connection and connect ok. Then on the next boot i have to go through the same procedure to connect.
I have checked that the working connection had been saved for the next boot and all is ok but it will not do so as the system says the modem may be switched off.
I have now tried all official releases since Dingo and all have the same problem.
If it helps i can pm you the pmodem diag .gz for dingo and 430.

it appears that we have a wifi hardware problem since puppy dingo4 on certain machines with inbuilt cards.

tubby wrote:

I have to switch the modem off then on before the system sees it
...
the system says the modem may be switched off.

tubby,
your information is unclear. You interchange the word "wifi" and "modem" too freely.
Be aware that I was referring to wifi adaptors; these create standard network interfaces in Linux.
Modems (including wireless modems) are completely different devices.

If you need to turn the modem off/on to get wifi working, this may be due to some form of hardware conflict between the two devices, but I'm just trying to make it clear that you are dealing with two distinctly separate devices: a dial-up modem, and a wifi adaptor.

Thanks for clearing the confusion i had over the two interfaces, i had forgotten that there is also an inbuilt 56k modem( it is tucked away under pull down flap along with the ethernet and external monitor connectors).
The wifi interface is listed as MPC13A-20 the FCC ID:CJ6PA3070WL, the model is PP400E also known as P4000.
If you can shed some light on why it is detected and initialized ok in Dingo but no other 4series it would no doubt help other puppy users who have the same interfaces.

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