I have a problem with WMP 10. Video clips often stops for a longer
period of time (often several seconds). Same thing happens in
Zoom Player Pro 4.02, so it's not just WMP.

Maybe it's because I haven't got a driver for my sound card yet
(see: but it could
also be my graphic card driver, which is this one at the moment:
.

--
Regards
Madsen

En , The_Rock va escriure:


Perhaps one should blame IBM and the lack of support of 32-bit mode inside
OS/2 v.1.x which forced "everyone" to stay in 16-bit mode for some *years*
then.


Since Linux is happily powering 64-bit PCs for some time now, I guess the
transition will not be quite as abrupt.
Just a guess, though.


Antoine

En ,
Charlie Russel - MVP va escriure:

Night batch programs routinely run for several hours. This was so before my
father heard about computers, in fact.


Yes. I remember the first big hardware upgrade too (on the mainframe, that
is). Numbers like this showed up, particularly about those night batch
times.
Normally, by the end of the quarter, the guy that is programming the job did
succeed at filling the now "empty" time with subsequent very interesting
queries.

And the best thing is that the computer won't complain (try this with your
assistant to see if it's the same.)

That's the sort of reasons why I love computers.


Yet right now, it becomes more and more difficult to find printers not
GDI-driven and with something else than USB, at least unless you agree to
pay a LOT more just to have a basic Centronics on the rear side and a
simple-minded page description language interpretor...


Antoine

En ,
ChrisGB va escriure:

WinXP was the second release (after Win2000: it is really NT5.1, remember)
of the third version (3.x=1st, 4.0=2nd) of the NT 32-bit operating system.
Its maturation lasts for more than a year. At that time it was one of the
two flagships (the other being Office XP) in MS portfolio, with the relevant
scrutinity. So any serious issue would have be a severe problem for MS.

OTOH, x64 NT is the first release of the first version of this branch of the
kernel; the processor it runs onto is hardly available in quantities for 2
years; it has to deal with the mix of 32-bit and 64-bit code (OK, 32-bit NT
dealt with 16-bit WOW/NTVDM, that could be compared); it is seen as
"experimental" (read "bleding edge" if you prefer) by about everyone, and
certainly by the markets (I guess nobody will make a fuss about the selling
numbers for it in the spring of 2006, unless of course the people at
comp.os.linux.advocacy to highlight it "does not sell well since the market
share is below the one for XP on IA32"... Etc.

They are hardly comparable.


Remember: before XP was released, there was 2000, earlier there was NT4, and
earlier again NT3.5. If you expect something like XP (or Win95), you'll see
NT3.5 as "released too early." But if MS had not released NT3.5 at that
moment, quite simply there will be no XP right now, and we will all using
Win03 v.4.99.6789, successor of the successor of WinME, sitting atop of a
MSDOS 8.2 kernel (but of course marketing guys will have hidden it even
more).


Certainly less than 2 years ;-). And when I take a look at the building time
of the driver I am using, while those in the last century are becoming
really scarse, those build in 2002 or 2003 are overwhelming.


Antoine

The only problem with that is that this is a new OS. The OS was in beta for
a year and was announced long before that, and yet most of the
hardware/peripheral manufacturers are still saying "we are evaluating our
strategy for 64-bit". Why is that? There has been plenty of time for them
to get their x64 drivers written, but they just haven't done that. The
reason is simple, though: with any new OS there is often a "wait and see"
approach taken. These companies are waiting to see just how widely x64 will
be adopted before they devote time and money to developing for it. That's
perfectly reasonable from a business perspective.

From my perspective, I have always believed that Windows x64 would be big
and definitely sell in the millions of units. Apparently the HPs, Canons,
and Logitechs of the world weren't so sure, so they decided to play the
waiting game. You want Microsoft to hold off shipping until there is wider
support. The hardware people want to see large numbers of units shipping
before they develop the support, which they're not going to see until
Microsoft releases. So which comes first, the chicken or the egg? At some
point you have to quit holding your breath and waiting on the other guy and
release, and the support will have to follow. And that's what Microsoft
did.

I'm sorry if you feel like you've been cheated somehow because you were an
early adopter, but that's why they call it the bleeding edge. Lack of
support from third parties isn't Microsoft's fault, and it is unproductive
to try to blame them for it. If you do your research on products before
deciding to take the x64 plunge, you should be adequately prepared (i.e.,
have the appropriate drivers or at least know what drivers you will have to
wait for). There are no suprises here unless you blindly jumped in.

No. There's no retail release because Microsoft decided that the best way
to get widespread adoption was to make it OEM-only, ensuring that the
overwhelming majority of people who buy it get it preinstalled on a new PC
with hardware that is supported. The alternative is to have to try to
support an unknown number of retail customers who have problems with x64
(i.e., bought x64 by mistake, didn't realize that they required a 64-bit
CPU, don't have drivers for all of their hardware and don't understand that
Microsoft doesn't write the drivers, etc). Besides, the OEM market is far,
far, larger than retail. Retail OS sales make up a very small percentage of
total OS sales for Microsoft.

So in summary, there's no retail because it's easier to release it OEM only,
and not having a retail presence will not significantly impact sales.

I would be leaning towards a driver issue. I had similar problems with some
of the pre-release versions of my video drivers.

If you read the thread you could have saved typing. Or, maybe is was just
too complex.