Jim, I don't think Jay tried to glorify him self (kidding), he just try to help in this issue, we are proposing solutions here to problems that currently we do not have, and that are not so issolated that we can just pin out the problem at a glance.
Jay, as you said we have not issolated sympthoms on the issue, I'm just gave another point of view of what could cause a problem like this. On the other message you wrote actually there's a great diff in the networking between XP-Home and XP-Pro but neved had problems with that before, and that make me think a little bit more on that, and perhaps the problem could be also associated with it or with Windows Firewall (introduced on SP2) or any other firewall like Norton's. The best test enviroment could be a fresh install of XP SP1, either home or pro, no internet access, and just istall PODS, if it works then we have not an OS issue. Then start installing other things and see when it fails, yes it is "try and fail", but may be a good aproach, this way you can provide us more specific info about what's going bad, and posibly we could help you better. Good Luck. Eduardo Orea. "Jay Ts" <[EMAIL PROTECTED]> escribió en el mensaje news:[EMAIL PROTECTED] > Eduardo Orea wrote: >> This could be an XP Home related issue. Perhaps something about the >> Administrator's rights on the file system or something alike. > > Eduardo, you might be onto something there. I forget the details, > but a couple of times while setting up my PODS workspace as a > network share, I was running into permissions problems using > PODS from another system. I solved that by adding a access list > entry for me (my user account) and giving it "Full Permissions" > on the shared directory and all subdirectories and contents. > No more problem after that. > > I don't know if that would fix anything for people running PODS with > the workspace on the same machine, but it might be worth looking into. > >> The second thing that comes to my mind is a low memory related issue, but >> I >> think that PODS should run fine, slower 'cause os swaping, but should run >> fine or should show an "OUT OF MEMORY" error. > > I totally agree. It is almost conceivable that a system that is > thrashing virtual memory very seriously might delay the network > connection attempt long enough for it to time out, but I highly > doubt that is the source of anyone's problem. > > Jay Ts > -- > Author of Using Samba, 2nd edition > Published by O'Reilly Media > http://www.oreilly.com/catalog/samba2/ > -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
