S
Stephan Rose
Well today was the last straw. I mean, considering more work than I
consider reasonable I got most my hardware in a reasonable working state...
However the last straw was handed to me today.
First off, WHY THE FLYING RATS ASS **** does it take almost 5 minutes to
move a 2 gig file on the same drive??? Move! ***NOT COPY*** for the reading
impaired. There is a distinct difference. That's just incomprehensible. It
shouldn't take more than mere milliseconds regardless of file size if it's
on the same drives as a move doesn't actually require data to be moved. It
only requires the directory entry of the file to be moved.
But what really got me is this. This one project I work on, uses a
security dongle for anti piracy and to store user access data. This dongle
uses built in standard USB drivers. So they are NOT 3rd party vendor
drivers but they are Microsofts own drivers. They don't work correctly. I
can't live without the dongle though.
There are workarounds if you're just a user of the software that needs
the dongle, but I'm actually one of the developers and none of said
workarounds will work when executing from inside Visual Studio. And I
don't feel like spending 10 minutes working around Vista's problem
everytime I go to recompile the exe to test something.
So byebye Vista and welcome back XP.
Ya know, doesn't matter how much you polish a turd. In the end, it's still
a turd. And this one a quite stinky one at that.
--
Stephan
2003 Yamaha R6
å›ã®ã“ã¨æ€ã„出ã™æ—¥ãªã‚“ã¦ãªã„ã®ã¯
å›ã®ã“ã¨å¿˜ã‚ŒãŸã¨ããŒãªã„ã‹ã‚‰
consider reasonable I got most my hardware in a reasonable working state...
However the last straw was handed to me today.
First off, WHY THE FLYING RATS ASS **** does it take almost 5 minutes to
move a 2 gig file on the same drive??? Move! ***NOT COPY*** for the reading
impaired. There is a distinct difference. That's just incomprehensible. It
shouldn't take more than mere milliseconds regardless of file size if it's
on the same drives as a move doesn't actually require data to be moved. It
only requires the directory entry of the file to be moved.
But what really got me is this. This one project I work on, uses a
security dongle for anti piracy and to store user access data. This dongle
uses built in standard USB drivers. So they are NOT 3rd party vendor
drivers but they are Microsofts own drivers. They don't work correctly. I
can't live without the dongle though.
There are workarounds if you're just a user of the software that needs
the dongle, but I'm actually one of the developers and none of said
workarounds will work when executing from inside Visual Studio. And I
don't feel like spending 10 minutes working around Vista's problem
everytime I go to recompile the exe to test something.
So byebye Vista and welcome back XP.
Ya know, doesn't matter how much you polish a turd. In the end, it's still
a turd. And this one a quite stinky one at that.
--
Stephan
2003 Yamaha R6
å›ã®ã“ã¨æ€ã„出ã™æ—¥ãªã‚“ã¦ãªã„ã®ã¯
å›ã®ã“ã¨å¿˜ã‚ŒãŸã¨ããŒãªã„ã‹ã‚‰