That's kinda amusing. However, BOOT.INI is invariable read-only, unless you have specifically un-done that yourself, and if you've un-done it, you probably know how to fix it.
Worst case scenario, you go and put your Windows disk in, and tell it to do a Repair Install.
If you actually read through what you posted there, the Wiki link, you'll realise that at no point did the computer ever actually decide that there was an F14 attacking them, that that was all a decision made by management not knowing how to interpret data, or willingly misinterpreting data.
Or you could probably even presume that even if it does have a changeable amount of RAM to carve out of system ram to use as video ram, that that limit cannot be set to "None".
That worked superbly for OS/2.. "A better DOS than DOS, a better Windows than Windows".. so of course, the vast majority of people continued to write their DOS and Windows software, and the few OS/2 ports of decent apps were awful.
You can still get OS/2, and in fact, I plan to do so, just to mess with it's current incarnation.. when I get around to buying a 500+GB hard drive and have a ton of space to mess with...
I did see a brand new ATM that was being installed near somewhere I frequent, and it was running OS/2. I asked the guy installing it, if he knew anything about the operating systems, and he laughed, and said that the small amount of ATMs in the world that run Windows, DOS, or some custom OS have something like 200% more service calls per year than the OS/2 ones, so most of the manufacturers that tried to go to Windows-based systems ended up getting pressured by their clients into going back to OS/2
Not for the highest priced lawyers in the world. Their first action is to sue you to take ownership of whatever it is that they claim is infringing, as well as all money that you have or ever could have made from it. If that total = 0, then they pick some suitably random 6 digit number.
What about if you're playing a video poker game, that has a 104% payout? Ie, if you play it properly, you are guaranteed a 4% return on your investment over time. Is that gambling?:D
Now, I'm pissed. I submitted this article on April 28th, and it has been PENDING on my submission list ever since. Today, this goes live, and I get no credit for it.
Hitchhiker's Guide was not rated as a Novice game. And if there's anything that anyone beyond the Novice category should have learned by then, it's "PICK UP EVERY DAMN THING"..
That whole puzzle, while complex, was very much towards the beginning of the game, and once you figured out you'd be running through that section a few more times collecting all the hints it would give you (which it did), you'd get yourself a save spot right at the start of the Vogon ship section.
Every time you pressed the button, without having everything in exactly the right place, it would give you hints about what you needed to do.
Then there was EMX, which gave you GCC and complete access to the OS/2 API for free. And allowed easy porting of Unix-ish programs.
But, yes, part of the problem for OS/2 development was that IBM did not very well support devs. Windows wasn't exactly really hip on that, either. Until there was MSDN, it cost a bunch of money to get documentation, and compilers that worked for Windows. However, there were some non-Microsoft entries.
The Borland C++ for OS/2, was complete and total garbage. Maybe if they'd made a better product, there'd be a little more life for that product.
IBM has had a very bad way of treating the smaller users and devs. It also didn't help that the parts of OS/2 that weren't extremely excellent (like the Workplace Shell) were extremely piss poor. (The multimedia support)
svn merge does not rollback. svn merge changes your file to equal whatever previous version you give it, and then you re-commit it to make the change like it never happened. If you want to undo the commit that you just did, the only way to do that is to go and edit the repository directly, and hope that no one did an update/checkout in the time it takes you to do that.
A better way for it to work, saying that you didn't want to erase the last commit, would be to put a command in the current HEAD "revert file.c to revision 802".
Well, I initially thought that this was the painful long process of processing a binary diff, on the receiving computer. This article, as well as glancing at the CPU meter shooting through the roof when someone does an update involving one of those 30mb binaries indicates that the svnserve is doing something distressingly weird.
I still can't believe that the -server- is having problems with processing like that, though. Since SVN stores each changeset as a seperate file, all it should have to do is send out the changeset. INstead, the server sits there doing -something- for 50% of the time, then spends the other 50% of the time sending it.
checkout/export log? I have searched for something like that, and have found no such option. Also told on #svn, that svnserve doesn't log accesses. How do you set that up?
Part of the reason I started using SVN was because of the ease of use of TortoiseSVN. There's nothing that I can find that could be easier for people who aren't into this kinda stuff.
The other people I am working with are game level builders, not code geeks. So, they've never used anything like this.
My "server" is my desktop machine, AMD Athlon XP 2000+. 30mb files take around 12 minutes or so to checkout. That's to a computer on the LAN. Add 8 or 9 of those to my project, and we're spending hours doing checkouts. Fortunatly most of those files never change, but when they do, that's an automatic 10-15 minutes of time that's going to be spent waiting by every person that gets an update after that.
Slashdot Mirror
That's kinda amusing. However, BOOT.INI is invariable read-only, unless you have specifically un-done that yourself, and if you've un-done it, you probably know how to fix it.
Worst case scenario, you go and put your Windows disk in, and tell it to do a Repair Install.
How absolutely useless is it, that it's a summarized version of the diffs, supposedly?
Why can't we see the actual source documents, and the diffs themselves?
17,000 laptops for school children across Nigeria? What do they teach in school, how to email 419 scams?
That would seem to be pretty strange, having the children being afraid of the U.S., considering they were both born here...
If you actually read through what you posted there, the Wiki link, you'll realise that at no point did the computer ever actually decide that there was an F14 attacking them, that that was all a decision made by management not knowing how to interpret data, or willingly misinterpreting data.
Is it $100 Billion for each of the 150 other WTO countries? That would make more sense, really.
:)
Isn't that $1 Quadrillion? Or would that be $100 Trillion ?
http://cakepoker.com/?share=112024Play poker at Cake Poker
Or you could probably even presume that even if it does have a changeable amount of RAM to carve out of system ram to use as video ram, that that limit cannot be set to "None".
That worked superbly for OS/2.. "A better DOS than DOS, a better Windows than Windows" .. so of course, the vast majority of people continued to write their DOS and Windows software, and the few OS/2 ports of decent apps were awful.
You can still get OS/2, and in fact, I plan to do so, just to mess with it's current incarnation.. when I get around to buying a 500+GB hard drive and have a ton of space to mess with...
I did see a brand new ATM that was being installed near somewhere I frequent, and it was running OS/2. I asked the guy installing it, if he knew anything about the operating systems, and he laughed, and said that the small amount of ATMs in the world that run Windows, DOS, or some custom OS have something like 200% more service calls per year than the OS/2 ones, so most of the manufacturers that tried to go to Windows-based systems ended up getting pressured by their clients into going back to OS/2
Then you're not using hardware acceleration
You could've done that in FreeBASIC in about 100k of downloads.
Wtf, CmdrTaco.. you're an editor.. do some editing. As submitted, this story is illegible.
Not for the highest priced lawyers in the world. Their first action is to sue you to take ownership of whatever it is that they claim is infringing, as well as all money that you have or ever could have made from it. If that total = 0, then they pick some suitably random 6 digit number.
What about if you're playing a video poker game, that has a 104% payout? Ie, if you play it properly, you are guaranteed a 4% return on your investment over time. Is that gambling? :D
(Yes, they exist)
Now, I'm pissed. I submitted this article on April 28th, and it has been PENDING on my submission list ever since. Today, this goes live, and I get no credit for it.
Good going, Slashdot.
APRIL FARKING 28TH
Hitchhiker's Guide was not rated as a Novice game. And if there's anything that anyone beyond the Novice category should have learned by then, it's "PICK UP EVERY DAMN THING"..
That whole puzzle, while complex, was very much towards the beginning of the game, and once you figured out you'd be running through that section a few more times collecting all the hints it would give you (which it did), you'd get yourself a save spot right at the start of the Vogon ship section.
Every time you pressed the button, without having everything in exactly the right place, it would give you hints about what you needed to do.
Then there was EMX, which gave you GCC and complete access to the OS/2 API for free. And allowed easy porting of Unix-ish programs.
But, yes, part of the problem for OS/2 development was that IBM did not very well support devs. Windows wasn't exactly really hip on that, either. Until there was MSDN, it cost a bunch of money to get documentation, and compilers that worked for Windows. However, there were some non-Microsoft entries.
The Borland C++ for OS/2, was complete and total garbage. Maybe if they'd made a better product, there'd be a little more life for that product.
IBM has had a very bad way of treating the smaller users and devs. It also didn't help that the parts of OS/2 that weren't extremely excellent (like the Workplace Shell) were extremely piss poor. (The multimedia support)
Imagine - slashdot, the bastion of Linux users throughout the world - unnecessarily slitting the throat of a major Linux developer company.
The irony, it is delicious.
svn merge does not rollback. svn merge changes your file to equal whatever previous version you give it, and then you re-commit it to make the change like it never happened. If you want to undo the commit that you just did, the only way to do that is to go and edit the repository directly, and hope that no one did an update/checkout in the time it takes you to do that.
A better way for it to work, saying that you didn't want to erase the last commit, would be to put a command in the current HEAD "revert file.c to revision 802".
Well, I initially thought that this was the painful long process of processing a binary diff, on the receiving computer. This article, as well as glancing at the CPU meter shooting through the roof when someone does an update involving one of those 30mb binaries indicates that the svnserve is doing something distressingly weird.
I still can't believe that the -server- is having problems with processing like that, though. Since SVN stores each changeset as a seperate file, all it should have to do is send out the changeset. INstead, the server sits there doing -something- for 50% of the time, then spends the other 50% of the time sending it.
checkout/export log? I have searched for something like that, and have found no such option. Also told on #svn, that svnserve doesn't log accesses. How do you set that up?
Part of the reason I started using SVN was because of the ease of use of TortoiseSVN. There's nothing that I can find that could be easier for people who aren't into this kinda stuff.
The other people I am working with are game level builders, not code geeks. So, they've never used anything like this.
oh, and about 100mb of binaries, also .. but it never messes up the binaries, it just takes forever to update/commit/checkout on those
My "server" is my desktop machine, AMD Athlon XP 2000+. 30mb files take around 12 minutes or so to checkout. That's to a computer on the LAN. Add 8 or 9 of those to my project, and we're spending hours doing checkouts. Fortunatly most of those files never change, but when they do, that's an automatic 10-15 minutes of time that's going to be spent waiting by every person that gets an update after that.