Brent Newbury
May 3rd 03, 01:18 AM
Hi all,
[This is a long rant at Microsoft - although it isn't all
bad]
I've just been having problems with MSN Messenger. Me and
a significant other wanted to doodle using Whiteboard (as
you do). But the button to start Whiteboard didn't work.
So I tried Application Sharing, that didn't work either.
So then I tried Remote Assistance, no luck there. These
buttons were just doing nothing.
So I looked for hours, browsing the web, searching
Google.com, and then, when I was desperate, I used
Microsoft News Groups (always a last resort for me) and
found out why (with thanks to Jonathan Kay [MVP]).
Correct me if I'm wrong, but it's because MSN Messenger
doesn't have stand-alone support for Application Sharing,
Whiteboard, or Remote Assistance (through IM).
And because this was a significant other I wanted to
doodle with, I uninstalled MSN Messenger, and re-
installed Windows Messenger. And doodled away, and a
merry old time we had.
Then it dawned on me why I started using MSN Messenger in
the first place; it's because I couldn't transfer files
out using Windows Messenger.
With my network setup:
My Computer is running Windows XP Pro linked to my server.
My server is running Windows XP Pro (166MHz 128MB RAM -
yes Windows XP can run on this setup, slowly I might
add :D). With ICS enabled and no Firewall systems at all -
I'm as open as a Dutch brothel. My server is then
connected to the Internet through a Cable Modem. This
setup is usually called "daisy-chained".
So because Microsoft doesn't want to pull it's finger out
of it's ass, and make Windows Messenger File Transfer U-
PnP enabled, I can either sit on my ass and doodle with
someone but can't send them a file, or I can send them a
file, but not sit there and doodle.
Now I know Microsoft has been busy with the new launch of
Windows Server 2003 and the development of
Windows "Longhorn" as an ongoing process, but c'mon
guys... copy-and-paste a few thousand lines of code,
about 4 days of debuggin', and you'll get a few happy
Microsoft fans now ready to kiss that ass you doing an
awful lot of sitting on.
Regards,
Brent Newbury
[P.S. For those of you who think I hate Microsoft, this
will enlighten you: when I finish my Software Engineering
degree, I wana work for these people... I wana be a "Code
Monkey" for Microsoft]
[This is a long rant at Microsoft - although it isn't all
bad]
I've just been having problems with MSN Messenger. Me and
a significant other wanted to doodle using Whiteboard (as
you do). But the button to start Whiteboard didn't work.
So I tried Application Sharing, that didn't work either.
So then I tried Remote Assistance, no luck there. These
buttons were just doing nothing.
So I looked for hours, browsing the web, searching
Google.com, and then, when I was desperate, I used
Microsoft News Groups (always a last resort for me) and
found out why (with thanks to Jonathan Kay [MVP]).
Correct me if I'm wrong, but it's because MSN Messenger
doesn't have stand-alone support for Application Sharing,
Whiteboard, or Remote Assistance (through IM).
And because this was a significant other I wanted to
doodle with, I uninstalled MSN Messenger, and re-
installed Windows Messenger. And doodled away, and a
merry old time we had.
Then it dawned on me why I started using MSN Messenger in
the first place; it's because I couldn't transfer files
out using Windows Messenger.
With my network setup:
My Computer is running Windows XP Pro linked to my server.
My server is running Windows XP Pro (166MHz 128MB RAM -
yes Windows XP can run on this setup, slowly I might
add :D). With ICS enabled and no Firewall systems at all -
I'm as open as a Dutch brothel. My server is then
connected to the Internet through a Cable Modem. This
setup is usually called "daisy-chained".
So because Microsoft doesn't want to pull it's finger out
of it's ass, and make Windows Messenger File Transfer U-
PnP enabled, I can either sit on my ass and doodle with
someone but can't send them a file, or I can send them a
file, but not sit there and doodle.
Now I know Microsoft has been busy with the new launch of
Windows Server 2003 and the development of
Windows "Longhorn" as an ongoing process, but c'mon
guys... copy-and-paste a few thousand lines of code,
about 4 days of debuggin', and you'll get a few happy
Microsoft fans now ready to kiss that ass you doing an
awful lot of sitting on.
Regards,
Brent Newbury
[P.S. For those of you who think I hate Microsoft, this
will enlighten you: when I finish my Software Engineering
degree, I wana work for these people... I wana be a "Code
Monkey" for Microsoft]