From: Jamie Kahn Genet on 28 Apr 2010 10:30 Doug Anderson <ethelthelogremovethis(a)gmail.com> wrote: > jamiekg(a)wizardling.geek.nz (Jamie Kahn Genet) writes: > > > Jolly Roger <jollyroger(a)pobox.com> wrote: > > > > > In article <1jhnt0h.oibtzhzxpe2oN%jamiekg(a)wizardling.geek.nz>, > > > jamiekg(a)wizardling.geek.nz (Jamie Kahn Genet) wrote: > > > > > > > Jolly Roger <jollyroger(a)pobox.com> wrote: > > > > > > > > > In article <1jhn2fg.5rzkaw8cwea0N%jamiekg(a)wizardling.geek.nz>, > > > > > jamiekg(a)wizardling.geek.nz (Jamie Kahn Genet) wrote: > > > > > > > > > > > Doug Anderson <ethelthelogremovethis(a)gmail.com> wrote: > > > > > > > > > > > > > jamiekg(a)wizardling.geek.nz (Jamie Kahn Genet) writes: > > > > > > > > > > > > > > > OSX 10.5.8, been happening for a couple years. No, zero machines > > > > > > > > with the same name are on my network. Yup - I've double and > > > > > > > > triple and quadruple checked this. In Network settings->WINS it > > > > > > > > always says "NAME is currently in use" no matter what I change > > > > > > > > it to. I change it to... say 'Dragon', apply - it still says > > > > > > > > it's in use. I change the computer name in Sharing prefs and > > > > > > > > later it's Dragon_(2) again. > > > > > > > > > > > > > > > > However I'd REALLY like it to accept and KEEP 'Crystalis' as my > > > > > > > > computer's name. Not Crystalis_(2). Not one of the other test > > > > > > > > names which all eventually become NAME_(2) anyway. > > > > > > > > > > > > > > > > I've put up with it for ages as it's a minor problem - I can > > > > > > > > just use IP addresses to connect, not hostnames that OSX keeps > > > > > > > > appending numbers to and thus wrecking (so braindead...). But > > > > > > > > for reasons I won't bore you with it's becoming more of a > > > > > > > > hassle. Any advice? > > > > > > > > > > > > > > Have you tried the usual way of setting your computer name: > > > > > > > > > > > > > > System Preferences -> Sharing -> Computer name: > > > > > > > > > > > > Yes, to no avail. It is later changed to NAME_(2) again. > > > > > > > > > > Are you running more than one network interface on that Mac? > > > > > > > > I have, but only one - Ethernet - is active. > > > > > > You sure about that? What output do you get when you do: > > > > > > ifconfig -a > > > > Crystalis:~ Jamie_Standard$ ifconfig -a > > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 > > inet 127.0.0.1 netmask 0xff000000 > > inet6 fd3e:9187:b2fe:7962:21e:c2ff:fea2:7f37 prefixlen 128 > > gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 > > stf0: flags=0<> mtu 1280 > > fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078 > > lladdr 00:1f:5b:ff:fe:0a:49:d8 > > media: autoselect <full-duplex> status: inactive > > supported media: autoselect <full-duplex> > > en1: flags=8823<UP,BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500 > > ether 00:1e:c2:a2:7f:37 > > media: autoselect (<unknown type>) status: inactive > > supported media: autoselect > > en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > > inet6 fe80::21e:c2ff:fe15:1af9%en0 prefixlen 64 scopeid 0x6 > > inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255 > > ether 00:1e:c2:15:1a:f9 > > media: autoselect (100baseTX <full-duplex,flow-control>) status: > > active > > supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP > > <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP > > <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX > > <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX > > <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT > > <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control> none > > en2: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > > ether 00:1f:5b:6e:ae:92 > > media: autoselect status: inactive > > supported media: none autoselect 10baseT/UTP <half-duplex> > > vmnet8: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu > > 1500 > > inet 192.168.119.1 netmask 0xffffff00 broadcast 192.168.119.255 > > ether 00:50:56:c0:00:08 > > vmnet1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu > > 1500 > > inet 192.168.225.1 netmask 0xffffff00 broadcast 192.168.225.255 > > ether 00:50:56:c0:00:01 > > -- > > I see you have these two vmnet interfaces that have assigned > ethernet addresses (and that don't show up as "inactive"). These are > maybe from running VMware? > > If you turn off VMware, then does en1 become your only interface with > an IP address assigned? And if so, can you name your computer as you > wish (using system preferences) in that case? Yeah, I thought of that, only Fusion isn't running and hasn't been for about a month (not been in the mood for any of the PC only games - that won't run well in Crossover - I use it for). -- If you're not part of the solution, you're part of the precipitate.
From: Jamie Kahn Genet on 28 Apr 2010 10:33 Jamie Kahn Genet <jamiekg(a)wizardling.geek.nz> wrote: > Doug Anderson <ethelthelogremovethis(a)gmail.com> wrote: > > > jamiekg(a)wizardling.geek.nz (Jamie Kahn Genet) writes: > > > > > Jolly Roger <jollyroger(a)pobox.com> wrote: > > > > > > > In article <1jhnt0h.oibtzhzxpe2oN%jamiekg(a)wizardling.geek.nz>, > > > > jamiekg(a)wizardling.geek.nz (Jamie Kahn Genet) wrote: > > > > > > > > > Jolly Roger <jollyroger(a)pobox.com> wrote: > > > > > > > > > > > In article <1jhn2fg.5rzkaw8cwea0N%jamiekg(a)wizardling.geek.nz>, > > > > > > jamiekg(a)wizardling.geek.nz (Jamie Kahn Genet) wrote: > > > > > > > > > > > > > Doug Anderson <ethelthelogremovethis(a)gmail.com> wrote: > > > > > > > > > > > > > > > jamiekg(a)wizardling.geek.nz (Jamie Kahn Genet) writes: > > > > > > > > > > > > > > > > > OSX 10.5.8, been happening for a couple years. No, zero > > > > > > > > > machines with the same name are on my network. Yup - I've > > > > > > > > > double and triple and quadruple checked this. In Network > > > > > > > > > settings->WINS it always says "NAME is currently in use" > > > > > > > > > no matter what I change it to. I change it to... say > > > > > > > > > 'Dragon', apply - it still says it's in use. I change the > > > > > > > > > computer name in Sharing prefs and later it's Dragon_(2) > > > > > > > > > again. > > > > > > > > > > > > > > > > > > However I'd REALLY like it to accept and KEEP 'Crystalis' > > > > > > > > > as my computer's name. Not Crystalis_(2). Not one of the > > > > > > > > > other test names which all eventually become NAME_(2) > > > > > > > > > anyway. > > > > > > > > > > > > > > > > > > I've put up with it for ages as it's a minor problem - I > > > > > > > > > can just use IP addresses to connect, not hostnames that > > > > > > > > > OSX keeps appending numbers to and thus wrecking (so > > > > > > > > > braindead...). But for reasons I won't bore you with it's > > > > > > > > > becoming more of a hassle. Any advice? > > > > > > > > > > > > > > > > Have you tried the usual way of setting your computer name: > > > > > > > > > > > > > > > > System Preferences -> Sharing -> Computer name: > > > > > > > > > > > > > > Yes, to no avail. It is later changed to NAME_(2) again. > > > > > > > > > > > > Are you running more than one network interface on that Mac? > > > > > > > > > > I have, but only one - Ethernet - is active. > > > > > > > > You sure about that? What output do you get when you do: > > > > > > > > ifconfig -a > > > > > > Crystalis:~ Jamie_Standard$ ifconfig -a > > > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 > > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 > > > inet 127.0.0.1 netmask 0xff000000 > > > inet6 fd3e:9187:b2fe:7962:21e:c2ff:fea2:7f37 prefixlen 128 > > > gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 > > > stf0: flags=0<> mtu 1280 > > > fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078 > > > lladdr 00:1f:5b:ff:fe:0a:49:d8 > > > media: autoselect <full-duplex> status: inactive > > > supported media: autoselect <full-duplex> > > > en1: flags=8823<UP,BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500 > > > ether 00:1e:c2:a2:7f:37 > > > media: autoselect (<unknown type>) status: inactive > > > supported media: autoselect > > > en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > > > inet6 fe80::21e:c2ff:fe15:1af9%en0 prefixlen 64 scopeid 0x6 > > > inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255 > > > ether 00:1e:c2:15:1a:f9 > > > media: autoselect (100baseTX <full-duplex,flow-control>) status: > > > active > > > supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP > > > <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP > > > <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX > > > <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX > > > <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT > > > <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control> none > > > en2: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > > > ether 00:1f:5b:6e:ae:92 > > > media: autoselect status: inactive > > > supported media: none autoselect 10baseT/UTP <half-duplex> > > > vmnet8: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu > > > 1500 > > > inet 192.168.119.1 netmask 0xffffff00 broadcast 192.168.119.255 > > > ether 00:50:56:c0:00:08 > > > vmnet1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu > > > 1500 > > > inet 192.168.225.1 netmask 0xffffff00 broadcast 192.168.225.255 > > > ether 00:50:56:c0:00:01 > > > -- > > > > I see you have these two vmnet interfaces that have assigned > > ethernet addresses (and that don't show up as "inactive"). These are > > maybe from running VMware? > > > > If you turn off VMware, then does en1 become your only interface with > > an IP address assigned? And if so, can you name your computer as you > > wish (using system preferences) in that case? > > Yeah, I thought of that, only Fusion isn't running and hasn't been for > about a month (not been in the mood for any of the PC only games - that > won't run well in Crossover - I use it for). But JR set me straight on that. Cheers Doug! :-) -- If you're not part of the solution, you're part of the precipitate.
From: Jamie Kahn Genet on 28 Apr 2010 10:42 Jolly Roger <jollyroger(a)pobox.com> wrote: > In article <1jhof4t.1l84u78s6i2djN%jamiekg(a)wizardling.geek.nz>, > jamiekg(a)wizardling.geek.nz (Jamie Kahn Genet) wrote: > > > Jolly Roger <jollyroger(a)pobox.com> wrote: > > > > > In article <1jhnt0h.oibtzhzxpe2oN%jamiekg(a)wizardling.geek.nz>, > > > jamiekg(a)wizardling.geek.nz (Jamie Kahn Genet) wrote: > > > > > > > Jolly Roger <jollyroger(a)pobox.com> wrote: > > > > > > > > > In article <1jhn2fg.5rzkaw8cwea0N%jamiekg(a)wizardling.geek.nz>, > > > > > jamiekg(a)wizardling.geek.nz (Jamie Kahn Genet) wrote: > > > > > > > > > > > Doug Anderson <ethelthelogremovethis(a)gmail.com> wrote: > > > > > > > > > > > > > jamiekg(a)wizardling.geek.nz (Jamie Kahn Genet) writes: > > > > > > > > > > > > > > > OSX 10.5.8, been happening for a couple years. No, zero machines > > > > > > > > with the same name are on my network. Yup - I've double and > > > > > > > > triple and quadruple checked this. In Network settings->WINS it > > > > > > > > always says "NAME is currently in use" no matter what I change > > > > > > > > it to. I change it to... say 'Dragon', apply - it still says > > > > > > > > it's in use. I change the computer name in Sharing prefs and > > > > > > > > later it's Dragon_(2) again. > > > > > > > > > > > > > > > > However I'd REALLY like it to accept and KEEP 'Crystalis' as my > > > > > > > > computer's name. Not Crystalis_(2). Not one of the other test > > > > > > > > names which all eventually become NAME_(2) anyway. > > > > > > > > > > > > > > > > I've put up with it for ages as it's a minor problem - I can > > > > > > > > just use IP addresses to connect, not hostnames that OSX keeps > > > > > > > > appending numbers to and thus wrecking (so braindead...). But > > > > > > > > for reasons I won't bore you with it's becoming more of a > > > > > > > > hassle. Any advice? > > > > > > > > > > > > > > Have you tried the usual way of setting your computer name: > > > > > > > > > > > > > > System Preferences -> Sharing -> Computer name: > > > > > > > > > > > > Yes, to no avail. It is later changed to NAME_(2) again. > > > > > > > > > > Are you running more than one network interface on that Mac? > > > > > > > > I have, but only one - Ethernet - is active. > > > > > > You sure about that? What output do you get when you do: > > > > > > ifconfig -a > > > (snip) > > vmnet8: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu > > 1500 > > inet 192.168.119.1 netmask 0xffffff00 broadcast 192.168.119.255 > > ether 00:50:56:c0:00:08 > > vmnet1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu > > 1500 > > inet 192.168.225.1 netmask 0xffffff00 broadcast 192.168.225.255 > > ether 00:50:56:c0:00:01 > > There's your problem. The last interface listed, vmnet1, is an Ethernet > interface from VMware Fusion. It's using the same name. > > So to solve the issue, go into VMware Fusion, start Windows if needed, > right-click My Computer and choose Properties, and change the computer > name to something other than Crystalis. Ah - problem. My computer's name in XP isn't Crystalis. I thought that was odd anyway - I don't usually name two things the same. But i assumed I must have. However in My Computer's Properties->Computer Name->Change... [name] I see the name is 'jamie-bc968d85a'. I'm not seeing 'Crystalis' anywhere. -- If you're not part of the solution, you're part of the precipitate.
From: Jamie Kahn Genet on 28 Apr 2010 10:44 Jamie Kahn Genet <jamiekg(a)wizardling.geek.nz> wrote: > Jamie Kahn Genet <jamiekg(a)wizardling.geek.nz> wrote: > > > Doug Anderson <ethelthelogremovethis(a)gmail.com> wrote: > > > > > jamiekg(a)wizardling.geek.nz (Jamie Kahn Genet) writes: > > > > > > > Jolly Roger <jollyroger(a)pobox.com> wrote: > > > > > > > > > In article <1jhnt0h.oibtzhzxpe2oN%jamiekg(a)wizardling.geek.nz>, > > > > > jamiekg(a)wizardling.geek.nz (Jamie Kahn Genet) wrote: > > > > > > > > > > > Jolly Roger <jollyroger(a)pobox.com> wrote: > > > > > > > > > > > > > In article <1jhn2fg.5rzkaw8cwea0N%jamiekg(a)wizardling.geek.nz>, > > > > > > > jamiekg(a)wizardling.geek.nz (Jamie Kahn Genet) wrote: > > > > > > > > > > > > > > > Doug Anderson <ethelthelogremovethis(a)gmail.com> wrote: > > > > > > > > > > > > > > > > > jamiekg(a)wizardling.geek.nz (Jamie Kahn Genet) writes: > > > > > > > > > > > > > > > > > > > OSX 10.5.8, been happening for a couple years. No, zero > > > > > > > > > > machines with the same name are on my network. Yup - I've > > > > > > > > > > double and triple and quadruple checked this. In Network > > > > > > > > > > settings->WINS it always says "NAME is currently in use" > > > > > > > > > > no matter what I change it to. I change it to... say > > > > > > > > > > 'Dragon', apply - it still says it's in use. I change the > > > > > > > > > > computer name in Sharing prefs and later it's Dragon_(2) > > > > > > > > > > again. > > > > > > > > > > > > > > > > > > > > However I'd REALLY like it to accept and KEEP 'Crystalis' > > > > > > > > > > as my computer's name. Not Crystalis_(2). Not one of the > > > > > > > > > > other test names which all eventually become NAME_(2) > > > > > > > > > > anyway. > > > > > > > > > > > > > > > > > > > > I've put up with it for ages as it's a minor problem - I > > > > > > > > > > can just use IP addresses to connect, not hostnames that > > > > > > > > > > OSX keeps appending numbers to and thus wrecking (so > > > > > > > > > > braindead...). But for reasons I won't bore you with it's > > > > > > > > > > becoming more of a hassle. Any advice? > > > > > > > > > > > > > > > > > > Have you tried the usual way of setting your computer name: > > > > > > > > > > > > > > > > > > System Preferences -> Sharing -> Computer name: > > > > > > > > > > > > > > > > Yes, to no avail. It is later changed to NAME_(2) again. > > > > > > > > > > > > > > Are you running more than one network interface on that Mac? > > > > > > > > > > > > I have, but only one - Ethernet - is active. > > > > > > > > > > You sure about that? What output do you get when you do: > > > > > > > > > > ifconfig -a > > > > > > > > Crystalis:~ Jamie_Standard$ ifconfig -a > > > > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 > > > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 > > > > inet 127.0.0.1 netmask 0xff000000 > > > > inet6 fd3e:9187:b2fe:7962:21e:c2ff:fea2:7f37 prefixlen 128 > > > > gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 > > > > stf0: flags=0<> mtu 1280 > > > > fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078 > > > > lladdr 00:1f:5b:ff:fe:0a:49:d8 > > > > media: autoselect <full-duplex> status: inactive > > > > supported media: autoselect <full-duplex> > > > > en1: flags=8823<UP,BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500 > > > > ether 00:1e:c2:a2:7f:37 > > > > media: autoselect (<unknown type>) status: inactive > > > > supported media: autoselect > > > > en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > > > > inet6 fe80::21e:c2ff:fe15:1af9%en0 prefixlen 64 scopeid 0x6 > > > > inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255 > > > > ether 00:1e:c2:15:1a:f9 > > > > media: autoselect (100baseTX <full-duplex,flow-control>) status: > > > > active > > > > supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP > > > > <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP > > > > <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX > > > > <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX > > > > <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT > > > > <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control> none > > > > en2: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > > > > ether 00:1f:5b:6e:ae:92 > > > > media: autoselect status: inactive > > > > supported media: none autoselect 10baseT/UTP <half-duplex> > > > > vmnet8: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu > > > > 1500 > > > > inet 192.168.119.1 netmask 0xffffff00 broadcast 192.168.119.255 > > > > ether 00:50:56:c0:00:08 > > > > vmnet1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu > > > > 1500 > > > > inet 192.168.225.1 netmask 0xffffff00 broadcast 192.168.225.255 > > > > ether 00:50:56:c0:00:01 > > > > -- > > > > > > I see you have these two vmnet interfaces that have assigned > > > ethernet addresses (and that don't show up as "inactive"). These are > > > maybe from running VMware? > > > > > > If you turn off VMware, then does en1 become your only interface with > > > an IP address assigned? And if so, can you name your computer as you > > > wish (using system preferences) in that case? > > > > Yeah, I thought of that, only Fusion isn't running and hasn't been for > > about a month (not been in the mood for any of the PC only games - that > > won't run well in Crossover - I use it for). > > But JR set me straight on that. Cheers Doug! :-) Drat - I see 'Crystalis' nowhere in XP that I can find. The computer's name there is 'jamie-bc968d85a' which Fusion must've named it by default based on my name. -- If you're not part of the solution, you're part of the precipitate.
From: Jolly Roger on 28 Apr 2010 11:00
In article <1jhovbz.6kt87owderkN%jamiekg(a)wizardling.geek.nz>, jamiekg(a)wizardling.geek.nz (Jamie Kahn Genet) wrote: > Jolly Roger <jollyroger(a)pobox.com> wrote: > > > There's your problem. The last interface listed, vmnet1, is an Ethernet > > interface from VMware Fusion. It's using the same name. > > > > So to solve the issue, go into VMware Fusion, start Windows if needed, > > right-click My Computer and choose Properties, and change the computer > > name to something other than Crystalis. > > Ah - problem. My computer's name in XP isn't Crystalis. I thought that > was odd anyway - I don't usually name two things the same. But i assumed > I must have. However in My Computer's Properties->Computer > Name->Change... [name] I see the name is 'jamie-bc968d85a'. I'm not > seeing 'Crystalis' anywhere. Hmm... I'm afraid you'll have to talk directly with VMware support regarding whether you can influence how Fusion implements these interfaces, including what name they use for WINS service. It appears VMware Fusion always uses 16-bit IP block addresses. Here's what I have on my system: vmnet1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 ether 00:50:56:c0:00:01 inet 192.168.61.1 netmask 0xffffff00 broadcast 192.168.61.255 vmnet8: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 ether 00:50:56:c0:00:08 inet 192.168.210.1 netmask 0xffffff00 broadcast 192.168.210.255 I suppose, then, that I'm not seeing this problem on my system because my network uses the 24-bit IP block (10.0.0.0 through 10.255.255.255 range), which means 16-bit IP block addresses aren't on the same subnet. In the mean time, you might consider simply changing your router configuration to use the 24-bit IP block as a work-around solution. -- Send responses to the relevant news group rather than email to me. E-mail sent to this address may be devoured by my very hungry SPAM filter. Due to Google's refusal to prevent spammers from posting messages through their servers, I often ignore posts from Google Groups. Use a real news client if you want me to see your posts. JR |