Do you have two NIC cards? I suspect you tech guy is confused. Even if you had two IP addresses that shouldn't make much difference. To check your IP address open a terminal and type ifconfig.

Hi. Sadly I wasn't able to do this as the system is gradually being upgraded to Windows 7 this week and I didn't want to risk "rocking the boat."

He did tell me what he thought the problem was though; apparently the Fatdog system is failing to release its IP address so it's showing up as a "ghost computer" on the network.

Maybe if I'm unable to investigate this further it's better if I write this off, especially if no one else is experiencing this problem when running Fatdog (or any other Puppy) on a networked Windows XP Pro system.

I was wondering if there are plans to include a System Monitor in FD500.

I boot FD500 with the .sfs for 32 bit libraries and the .sfs for 32-bit OxygenOffice works just fine.
I like gkrellm (small, efficient, and multi-functional) and I tried ttuuxxx's pet from here:
http://www.murga-linux.com/puppy/viewtopic.php?t=39202

Do you have two NIC cards? I suspect you tech guy is confused. Even if you had two IP addresses that shouldn't make much difference. To check your IP address open a terminal and type ifconfig.

Hi. Sadly I wasn't able to do this as the system is gradually being upgraded to Windows 7 this week and I didn't want to risk "rocking the boat."

He did tell me what he thought the problem was though; apparently the Fatdog system is failing to release its IP address so it's showing up as a "ghost computer" on the network.

Maybe if I'm unable to investigate this further it's better if I write this off, especially if no one else is experiencing this problem when running Fatdog (or any other Puppy) on a networked Windows XP Pro system.

Thanks for your attention anyway,

CP .

Can you set the network to accept a static IP?

That way the DHCP lease expiring would not be an issue.

Also...
We had a similar "problem" on a LAN with two IP addresses for a box with ethernet and wifi connections, both of which were being connected to the network. If it's not the lease issue, that might well be the ticket?

Or...
To set the puppy to keep up one can set the ip to go down and back up at intervals more suitable to the msWindows LAN.

If you reconnect too quickly (ie too soon) you will get multiple IP's listed on your LAN. (Sixty seconds or more is required for most DNS records to reset.) The timeouts vary, so check with your local support.

Yes, you'll see a button for that in the network wizard. You'll want to make sure that any static address you use is available and out of the DHCP server's range.

Quote:

We had a similar "problem" on a LAN with two IP addresses for a box with ethernet and wifi connections, both of which were being connected to the network. If it's not the lease issue, that might well be the ticket?

That's only possible if you have a network cable connected and you configure your wireless card to connect. Your wireless card will not just connect on it's own, unless you have configured it to do so. If you open a terminal and type ifconfig you'll get something like this (probably not this long):

wlan0 --- This is my wifi card. I gave it an address of 192.168.1.220.

Your interface names will vary, except for lo and probably eth0. In this example I have three ip addresses and all of my interfaces are up so ifconfig shows their status. If I had not caused all of those interfaces to be active, ifconfig would have just shown the lo interface and the interface I was actually using.

I suspect that you're using Windows, and Windows gets an IP address from your DHCP server, then when you shutdown/hybernate and Windows doesn't release that address. Then you boot up Fatdog64 and it gets an IP address from your DHCP server for that same MAC address. You might try opening a terminal on Windows (Start-run-cmd) and typing ipconfig /release and then shutting down. I don't know why you IT guy cares if your MAC address has two address assigned to it unless your running out of addresses.

I installed the hpijs_print and hplip_scan pets today. I am glad to say my printer works great. This is an HP PSC 1200 series. The scanner didn't fare so well. I received an error during device I/O. But I am very happy to have a printer. Thanks

I installed the hpijs_print and hplip_scan pets today. I am glad to say my printer works great. This is an HP PSC 1200 series. The scanner didn't fare so well. I received an error during device I/O. But I am very happy to have a printer. Thanks

I installed the hpijs_print and hplip_scan pets today. I am glad to say my printer works great. This is an HP PSC 1200 series. The scanner didn't fare so well. I received an error during device I/O.

Thanks for the feedback. I have tested these packages successfully in 511 on both a Deskjet and a Photosmart. So I don't know why a PSC would behave differently. I'm assuming that scanning worked with a 32-bit Puppy? Which HP package did you use there?

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