RE: 64 bit Windows...

["Jones, John \(US\)" <John.Jones@xxxxxxxxxx>]

I think what Dr. Frank said was that when they did the re-engineering
for 64-bit, they actually took it to 128-bit.  So when the hardware
catches up the OS will be ready.

John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787  F: +1-312-601-1782
john.jones@xxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of pnelson@xxxxxxxxxx
Sent: Thursday, April 28, 2005 8:29 AM
To: Midrange Systems Technical Discussion
Subject: RE: 64 bit Windows...


I once heard Frank Soltis say (perhaps it was about 5 years ago) that
the AS/400 is at the point where Microsoft and Intel want to be in 5
years, and when they get there, IBM can flip some switches and go to 96
or 128 bit processors (and your software will still run).

Nice crystal ball, huh?


Paul Nelson
Arbor Solutions, Inc.
708-670-6978  Cell
pnelson@xxxxxxxxxx




-----midrange-l-bounces@xxxxxxxxxxxx wrote: -----

To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
From: "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx> Sent by:
midrange-l-bounces@xxxxxxxxxxxx
Date: 04/28/2005 08:05AM
Subject: RE: 64 bit Windows...

> From: Walden H. Leverich
>
> I know what I think everytime I read a statement that's along the
lines
> of "so what, we've had that for xxx years, and you're just getting it 
> now." I think, "so what, I've got it now too. What do you have that I 
> don't have w/my windows solution." Look, Ford was pumping out Model Ts

> long before Toyota heard of a car, but that doesn't mean that I sould
be
> driving a Model T today. What you provided me yesterday is useless, I 
> can get it anywhere, what are you going to provide me tomorrow?

Oh ugh. I'll respond, primarily because I feel weird if I don't respond
to a Walden Wuvs Windows (C) post <grin>. But this is a REALLY bad
analogy. The iSeries is hardly a Model T. It's a hemi-powered Mustang
convertible. We had the technology ten years ago, and we've made it
work.

And that's the issue. Windows is JUST BARELY getting into the world of
64-bit. And if you remember the pain and suffering of moving from 16-bit
to 32-bit, you'd be wildly over-optimistic to expect a smooth transition
here. I don't expect 64-bit Windows to be fully functional for years.

When we say we've had a feature for ten years, we mean we've had it,
worked out the kinks, and incorporated it into our base package from the
ground up.

Typically when Windows says they have a feature, it means they've got it
in alpha test stage on a few selected applications, with a nasty
thunking interface for everyone else (those of you old enough to
remember 16-bit Windows probably remember "thunking" - for the
edification of everybody else, that was the official name for using
16-bit pointers with a "32-bit" interface).

Joe

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx  Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.




This email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this email without the author's prior permission.  
We have taken precautions to minimize the risk of transmitting software 
viruses, but we advise you to carry out your own virus checks on any attachment 
to this message.  We cannot accept liability for any loss or damage caused by 
software viruses.  The information contained in this communication may be 
confidential and may be subject to the attorney-client privilege. If you are 
the intended recipient and you do not wish to receive similar electronic 
messages from us in the future then please respond to the sender to this effect.