! Windows 7 Sucks

How much do you charging to suck my cock? Can your daughter do it
cheaply for me? Please reply soon.



Microsoft Rippoff wrote:
Windows 7 is the new Windows ME.

IE9 sucks really bad too.

Windows 7 64-bit sucks even worse.

Don't buy it. Insist on XP or Mac!

Hope this helps.



--

Al Sparber - PVII
http://www.projectseven.com
Dreamweaver Menus | Galleries | Widgets

On 30/11/2011 03:34, Zaidy036 wrote:

Maybe one of these will help:
http://www.filecx.com/search/epson_1200/ukw/1


?

On 11/29/2011, SC Tom posted:

Firefox has one big advantage. It has a *selectable* default folder
for internet downloaded images.

So does IE9 and IE8. Not that hard to do; don't know how easy it is for
Firefox.

Easier than for IE9. Since IE9 is pretty easy, you can tell that it isn't
hard for FF.

Without even looking at Help, it took me 30 seconds, because at first I
looked in the wrong place :-)

Like I said, I haven't used FF in forever, and didn't have installed long
enough to search for things like that. IE9, I looked up how to do it after my
first download. IE8 wasn't quite as simple, but still wasn't hard to do (as
I'm sure you know :-) ).

For me the difference is that in Firefox, the setting is where you
might expect it to be, whereas in Internet Explorer 9, it's in some
out-of-the-way place. So in FF, I found it just by looking, but in IE9
I had to find it by using Help.

--
Gene E. Bloch (Stumbling Bloch)

It's nice to hear from someone that knows exactly what they're talkling
about on this newsgroup. It's been a long time since we've had a poster
who tells it like it is. I've test that hunk a **** windows 7 and
promply abondened it and still use windows xp pro stolen edition.

Microsoft Rippoff wrote:

Windows 7 is the new Windows ME.

IE9 sucks really bad too.

Windows 7 64-bit sucks even worse.

Don't buy it. Insist on XP or Mac!

Hope this helps.

--

http://tinyurl.com/66skkxb

--
The Grandmaster of the CyberFROG

Come get your ticket to CyberFROG city

Nay, Art thou decideth playeth ye simpleton games. *Some* of us know
proper manners

Very few. I used to take calls from *rank* noobs but got fired the first
day on the job for potty mouth,

Bur-ring, i'll get this one: WHAT'S YOUR PROBLEM JERK!!? We're here to
help you dickweed, ok, ok give the power cord the jiggily piggily
wiggily all the while pushing the power button repeatedly now take
everything out of your computer except the power supply and *one* stick
of ram. Ok get the next sucker on the phone.

Deirdre Straughan (Roxio) is a LIAR (Deirdre McFibber)

There's the employer and the employee and the FROGGER and the FROGEE,
which one are you?

Hamster isn't a newsreader it's a mistake!

El-Gonzo Jackson FROGS both me and Chuckcar (I just got EL-FROG-OED!!)

I hate them both, With useless bogus bull**** you need at least *three*
fulltime jobs to afford either one of them

I'm a fulltime text *only* man on usenet now. The rest of the world
downloads the binary files not me i can't afford thousands of dollars a
month

VBB = Volume based billing. How much can we force up your arse sir?

UBB = User based bullFROGGING

Master Juba was a black man imitating a white man imitating a black man

Using my technical prowess and computer abilities to answer questions
beyond the realm of understandability

Regards Tony... Making usenet better for everyone everyday

This sig file was compiled via my journeys through usenet

In message , Mortimer
writes:
[]
In most respects, Windows 7 works perfectly for me.

(For the month or two I had a 7 machine to play with, I found I disliked
it a lot less than I was expecting to: I think it's a "good" Windows, on
the whole. I even understood what they were trying to do with libraries
[basically, make links work properly, like they did in Unix], though
some of the implementation needs tweaking.)

The only downsides a

- no 64-bit driver is available for my Epson 1200 scanner so I need
to keep an XP machine for this

Actually, that's Epson's fault, not Microsoft's.

True.

No, I would say it _is_ Microsoft's, for making an OS (or OS variant)
which can't use older drivers. Why should hardware manufacturers have to
keep producing new drivers (especially for kit they no longer make -
don't know if that's the case in this case)?
[]
--
J. P. Gilliver. UMRA: 1960/1985 MB++G.5AL-IS-P--Ch++(p)Ar@T0H+Sh0!:`)DNAf

"We'd agreed to overlook each others' families and everything, and get married"
(The Trouble with Harry)

On 01/12/2011 3:45 AM, J. P. Gilliver (John) wrote:
In message , Mortimer
writes:
[]
In most respects, Windows 7 works perfectly for me.

(For the month or two I had a 7 machine to play with, I found I disliked
it a lot less than I was expecting to: I think it's a "good" Windows, on
the whole. I even understood what they were trying to do with libraries
[basically, make links work properly, like they did in Unix], though
some of the implementation needs tweaking.)

The only downsides a

- no 64-bit driver is available for my Epson 1200 scanner so I need
to keep an XP machine for this

Actually, that's Epson's fault, not Microsoft's.

True.

No, I would say it _is_ Microsoft's, for making an OS (or OS variant)
which can't use older drivers. Why should hardware manufacturers have to
keep producing new drivers (especially for kit they no longer make -
don't know if that's the case in this case)?
[]

This argument was beaten to death on a Linux group (very few mfrs
provide drivers for Linux).

The real issue is lack of standards. We're well past the time that
printers should be plug'n'play, and I don't mean that the OS installs a
driver when you plug in the printer. It's bizarre that one needs
different drivers for different printers made by the same manufacturer. Etc.

Wolf K.

"Wolf K" wrote in message news:Y3MBq.61861$%

Wolf K

Which Province (Ont. or Que -0500 ) are you located in ?? I am in the Mtl. area.
Just curios. Thanks

--
Peter
Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.
This posting is provided "AS IS" with no warranties, and confers no rights.
http://www.microsoft.com/protect

On 01/12/2011 10:16 AM, Peter Foldes wrote:

"Wolf K" wrote in message news:Y3MBq.61861$%

Wolf K

Which Province (Ont. or Que -0500 ) are you located in ?? I am in the
Mtl. area. Just curios. Thanks

Ontario.

"Wolf K" wrote in message
om...
On 01/12/2011 10:16 AM, Peter Foldes wrote:

"Wolf K" wrote in message news:Y3MBq.61861$%

Wolf K

Which Province (Ont. or Que -0500 ) are you located in ?? I am in the
Mtl. area. Just curios. Thanks

Ontario.

Thanks.I was guessing TO. I will be in Ont tomorrow. Going to Petiwawa to pick up
friend who is back from Afghanistan.

JS

On Thu, 1 Dec 2011 15:40:33 -0500, "Peter Foldes"
wrote:

"Wolf K" wrote in message
. com...
On 01/12/2011 10:16 AM, Peter Foldes wrote:

"Wolf K" wrote in message news:Y3MBq.61861$%

Wolf K

Which Province (Ont. or Que -0500 ) are you located in ?? I am in the
Mtl. area. Just curios. Thanks

Ontario.

Thanks.I was guessing TO. I will be in Ont tomorrow. Going to Petiwawa to pick up
friend who is back from Afghanistan.

If you're looking to hook up with locals, try Craig's list. It's
rather off topic here....

"J. P. Gilliver (John)" wrote in message
...
In message , Mortimer
writes:

No, I would say it _is_ Microsoft's, for making an OS (or OS variant)
which can't use older drivers. Why should hardware manufacturers have to
keep producing new drivers (especially for kit they no longer make - don't
know if that's the case in this case)?

Why should MS (or ANY OS maker) support all old hardware ad infinitum? In
order to
advance the OS, keep it able to use the latest hardware and keep it secure,
some things
must be left behind or you'd end up with a huge, ungainly mess. If the
manufacturer
doesn't support the newest OS, then MS certainly doesn't have the resources
to write
drivers for every piece of obsolete equipment out there.

Tom L

In ,
Tom Lake wrote:
"J. P. Gilliver (John)" wrote in message
...
In message ,
Mortimer writes:

No, I would say it _is_ Microsoft's, for making an OS (or OS variant)
which can't use older drivers. Why should hardware manufacturers
have to keep producing new drivers (especially for kit they no
longer make - don't know if that's the case in this case)?

Why should MS (or ANY OS maker) support all old hardware ad infinitum?
In order to advance the OS, keep it able to use the latest hardware
and keep it secure, some things must be left behind or you'd end up
with a huge, ungainly mess. If the manufacturer doesn't support the
newest OS, then MS certainly doesn't have the resources to write
drivers for every piece of obsolete equipment out there.

Tom L

In the early days, an OS was screwed big time if it didn't support the
legacy factor. You can have the world's greatest OS ever seen, but it is
totally worthless if it doesn't support the past. Same is true today. If
you burn bridges as you go, you will always lose.

Since most of the old people at Microsoft has retired. The new
replacements just don't know any better. And I see Microsoft getting
into trouble because of this. Even Microsoft had to layoff people in
recent times because of this (the first time in history). And it isn't
going to get better for Microsoft until they relearn this lesson. And if
they don't... well either Linux or the Mac (or something unknown to us
today) will just take over.

--
Bill
Gateway M465e ('06 era) - OE-QuoteFix v1.19.2
Centrino Core Duo T2400 1.83GHz - 2GB - Windows XP SP3

"BillW50" wrote in
:

In ,
Tom Lake wrote:
"J. P. Gilliver (John)" wrote
in message ...
In message
,
Mortimer writes:

No, I would say it _is_ Microsoft's, for making an OS (or
OS variant) which can't use older drivers. Why should
hardware manufacturers have to keep producing new drivers
(especially for kit they no longer make - don't know if
that's the case in this case)?

Why should MS (or ANY OS maker) support all old hardware
ad infinitum? In order to advance the OS, keep it able to
use the latest hardware and keep it secure, some things
must be left behind or you'd end up with a huge, ungainly
mess. If the manufacturer doesn't support the newest OS,
then MS certainly doesn't have the resources to write
drivers for every piece of obsolete equipment out there.

Tom L

In the early days, an OS was screwed big time if it didn't
support the legacy factor. You can have the world's
greatest OS ever seen, but it is totally worthless if it
doesn't support the past. Same is true today. If you burn
bridges as you go, you will always lose.

"In the early days"....of what... teletypes and ASCII only
printers ?

Do today's printers even have an ASCII mode anymore whe

copy file.txt lpt1

actually prints the text file ?

Who's burning bridges here ?

The printer mfg's, not MS.


Since most of the old people at Microsoft has retired. The
new replacements just don't know any better. And I see
Microsoft getting into trouble because of this. Even
Microsoft had to layoff people in recent times because of
this (the first time in history).

I'm sure the layoffs were just like every other company on
Earth, the economy.....

.....not anything to do with whatever you're going on about
above....or below.


And it isn't going to get
better for Microsoft until they relearn this lesson. And if
they don't... well either Linux or the Mac (or something
unknown to us today) will just take over.

"BillW50" wrote in message ...
In ,
Tom Lake wrote:
"J. P. Gilliver (John)" wrote in message
...
In message ,
Mortimer writes:

No, I would say it _is_ Microsoft's, for making an OS (or OS variant)
which can't use older drivers. Why should hardware manufacturers
have to keep producing new drivers (especially for kit they no
longer make - don't know if that's the case in this case)?

Why should MS (or ANY OS maker) support all old hardware ad infinitum? In order to advance the OS, keep it able to
use the latest hardware and keep it secure, some things must be left behind or you'd end up with a huge, ungainly
mess. If the manufacturer doesn't support the newest OS, then MS certainly doesn't have the resources to write
drivers for every piece of obsolete equipment out there.

Tom L

In the early days, an OS was screwed big time if it didn't support the legacy factor. You can have the world's
greatest OS ever seen, but it is totally worthless if it doesn't support the past. Same is true today. If you burn
bridges as you go, you will always lose.

Since most of the old people at Microsoft has retired. The new replacements just don't know any better. And I see
Microsoft getting into trouble because of this. Even Microsoft had to layoff people in recent times because of this
(the first time in history). And it isn't going to get better for Microsoft until they relearn this lesson. And if
they don't... well either Linux or the Mac (or something unknown to us today) will just take over.


I don't think Linux or Mac (or something unknown) will ever displace Microsoft in my lifetime, but I'm sure someday in
the future, it may be replaced as the top dog.

Years ago (many, many), I tried OS/2 Warp for a little while. After installing it and rebooting, I no longer had a
CD-ROM drive. No OS/2 drivers for it, and none from (IIRC) Panasonic either. The only drives that were native in OS/2
were Matsu****a and a couple of others, and even though they own Panasonic now, they either didn't then or the two
drives weren't close enough for the Matsu****a drivers to work with my drive. I tried OS/2 with Windows 3.1 (upgrade)
thinking that might solve the problem, but no joy there either.

Another bad point was that I had an IBM Big Blue thermal printer, and I couldn't get either version of OS/2 to recognize
it either. IBM OS won't print to an INM printer? What's up with that? After a couple on months of searching and using it
(it was stable and speedy. No wonder; it had no drivers taking up memory), I finally went back to Windows. I've tinkered
with other OSes over the years, but have never left Windows for good. Works fine for me. If there's something about it I
don't like (and believe me, there's plenty), I can usually figure out a workaround or find a third party app to get 'er
done.
--
SC Tom

On 12/01/2011, SC Tom posted:
"BillW50" wrote in message
...
In ,
Tom Lake wrote:
"J. P. Gilliver (John)" wrote in message
...
In message ,
Mortimer writes:

No, I would say it _is_ Microsoft's, for making an OS (or OS variant)
which can't use older drivers. Why should hardware manufacturers
have to keep producing new drivers (especially for kit they no
longer make - don't know if that's the case in this case)?

Why should MS (or ANY OS maker) support all old hardware ad infinitum? In
order to advance the OS, keep it able to use the latest hardware and keep
it secure, some things must be left behind or you'd end up with a huge,
ungainly mess. If the manufacturer doesn't support the newest OS, then MS
certainly doesn't have the resources to write drivers for every piece of
obsolete equipment out there.

Tom L

In the early days, an OS was screwed big time if it didn't support the
legacy factor. You can have the world's greatest OS ever seen, but it is
totally worthless if it doesn't support the past. Same is true today. If
you burn bridges as you go, you will always lose.

Since most of the old people at Microsoft has retired. The new replacements
just don't know any better. And I see Microsoft getting into trouble
because of this. Even Microsoft had to layoff people in recent times
because of this (the first time in history). And it isn't going to get
better for Microsoft until they relearn this lesson. And if they don't...
well either Linux or the Mac (or something unknown to us today) will just
take over.


I don't think Linux or Mac (or something unknown) will ever displace
Microsoft in my lifetime, but I'm sure someday in the future, it may be
replaced as the top dog.

Years ago (many, many), I tried OS/2 Warp for a little while. After
installing it and rebooting, I no longer had a CD-ROM drive. No OS/2 drivers
for it, and none from (IIRC) Panasonic either. The only drives that were
native in OS/2 were Matsu****a and a couple of others, and even though they
own Panasonic now, they either didn't then or the two drives weren't close
enough for the Matsu****a drivers to work with my drive. I tried OS/2 with
Windows 3.1 (upgrade) thinking that might solve the problem, but no joy there
either.

Another bad point was that I had an IBM Big Blue thermal printer, and I
couldn't get either version of OS/2 to recognize it either. IBM OS won't
print to an INM printer? What's up with that? After a couple on months of
searching and using it (it was stable and speedy. No wonder; it had no
drivers taking up memory), I finally went back to Windows. I've tinkered with
other OSes over the years, but have never left Windows for good. Works fine
for me. If there's something about it I don't like (and believe me, there's
plenty), I can usually figure out a workaround or find a third party app to
get 'er done.

I once worked on some software for OS/2. Someone else was the video
expert writing drivers for a few video cards; this was before the card
manufacturers provided drivers.

I suggested to an appropriate person that IBM should be supporting some
other video cards ('twas a long time ago, so I've forgotten the
details). The reply was "We're not in the business of providing drivers
for non-IBM cards". I said no more...

And OS/2 has evaporated.

BTW, I did get to see a demo of some media-like software running under
that system; IIRC, it was really beautiful.

--
Gene E. Bloch (Stumbling Bloch)