There actually are apps out there that run as kernel mode drivers and access the RAM that is inaccessible to the OS, giving you a RAMdisk. Said RAMdisk can then be used for swap space. Yes, it sounds horribly ridiculous on the surface, but it does work.
Of course, if you want to get more ridiculous... do a RAID setup of some sort that allows you to start on the RAMdisk, then go to HDD when that's full.
Myself, I'll go for a different approach on my machine with both a 32-bit CPU and a chipset that has a hard 3 GiB limitation - I'm going to install an 8 GiB Mini-PCIe SSD, and either run ReadyBoost, or dedicate it to my swap file.
Actually, MOST consoles. (This'll be US-centric, here.)
Fairchild VES -> Fairchild Channel F System II Atari VCS -> Atari 2600 Jr. Mattel Intellivision -> Mattel Intellivision II Nintendo Entertainment System -> Nintendo NES-101 Sega Master System -> Sega Master System II Nintendo Game Boy -> Nintendo Game Boy Pocket Sega Genesis -> Sega Genesis 2 -> Majesco/Sega Genesis 3 (and that's not even counting the Sega Nomad) Nintendo Super NES -> Nintendo SNS-101 Sony PlayStation -> Sony PSone Nintendo Game Boy Advance -> Nintendo GBA SP -> Nintendo GB Micro Sony PlayStation 2 -> Sony Slimline PS2 Nintendo DS -> Nintendo DS Lite Sony PlayStation 3 -> Sony PS3 Slim
Anyway, I have seen very few times that people were, in the real world, accelerating faster than my car is capable of. Now, their cars are capable of accelerating faster, yes - my Miata is slower than almost every current minivan, FFS. But I actually press down my accelerator and wind it out to 7000 at times, and they don't.
I've got somewhere under 100 hp remaining in my Miata. (Worn out engine, one cylinder is WAY below spec on compression. Started with 116 hp.)
Want to know how I don't get squashed? I actually accelerate. I don't think I've ever had a situation where it was lacking in power, and that's even when a friend drove it in DC traffic. Never had a problem with taking advantage of gaps, and I can break the rear wheels loose in second in a corner, and that's with good tires. (Toyo Proxes T-1Rs, to be specific.)
And, I had a 52 hp Golf diesel. That thing... yes, it was dangerous. How did I not get squashed? I drove like a complete idiot. That car was all about momentum - if you can keep it, you're good. And if you can't keep it, play chicken with the semi truck in the way of merging in, he doesn't want to crash even if it won't be his fault. As for driving on city streets, I never found that to be a problem, because of the torque.
If you can't drive a 100 hp (at the crank) compact car in city traffic, you suck at driving.
The thing is, nobody has a clue on how to actually maintain a VW diesel here, yet they have insanely inflated resale value, so by the time you've bought one and brought it back up to correct levels of maintenance (and a VW that's improperly maintained WILL bite you in the ass, I know this all too well,) you could've bought a cheap gas car and the gasoline to make up the price difference over the lifetime of the car.
Financially, it does not make sense to buy a diesel car in the US, unless you have very, very picky requirements that rule out everything that isn't a VW Golf/Jetta. (A diesel pickup is another story, although while the engine in that Ram may well outlast you with care, the rest of the truck won't.)
However, they use less resources, have longer range, and have various other benefits (mmm, torque,) so there are reasons to buy one.
Pretty sure he's comparing SAE net horsepower with SAE net horsepower of modern cars more than SAE net vs. SAE gross.
Anyway, diesels are the same way about stump-pulling torque, except more so... while being a 4 or 6-cyl. As for the 4/6-cyl "boy racer" comments... there is more than one way to skin a cat, and there is a lot to be said about performance (or economy) through light weight.:) And, there were quite a few 4/6-cyl sports cars back then, too.
IIRC, the VW (it was a VW engine) 1.6 I4/2.0 I5/2.4 I6 indirect injection turbodiesels had 9 PSI of boost. Granted, for a diesel that's not considered much, especially today. But, IIRC, the "Volvo" D24 was 78 hp, versus 102 hp for the D24T that you're referring to.
Very true, but my point was more that the GSM protocol is specifically designed to handle quite a lot of users on one tower, and to keep them from stomping on each other or on other towers by keeping power down, whereas CB users usually blast full power (or even illegally high power.)
A modified GSM (or CDMA, or even AMPS) system would be interesting to see in amateur radio, where one should only use the minimum amount of power necessary to make the contact. Modified because you'd want to remove all billing, you'd want to use callsigns instead of phone numbers (dedicated equipment would be a must, because you'd have to run on amateur frequencies, so changing stuff like that wouldn't be a big issue,) and you'd want to remove the GSM encryption (amateur radio doesn't allow for encryption.)
Want to know the most flawed part of Windows security? Its users.
Both in number and in desire to run applications of their choosing.
Number, because malware writers in 2009 often do it either for the money (directly or indirectly,) or to create a botnet.
Desire to run applications of their choosing because of the dancing bunnies problem.
But, even if you do know how to avoid malware, unless you believe in disassembling every program you use, and studying the disassembly before running the program, and then running it in a machine hooked straight to another machine, both machines separate from your network and the internet, one machine running the malware, one running Wireshark, and reloading the OS, updates, and apps on both after every test run... the dancing bunnies problem is still a problem. The only reason that it's only a problem on Windows is... Windows is the biggest target by FAR. If Linux were a big target, you'd get dancing bunnies problems on Linux.
There are only three REAL solutions to the dancing bunnies problem.
1. Detect the payload - read: antivirus software 2. Require every single application that runs on the platform to go through that sandboxing and testing procedure - read: iPhone, and we all know how well that goes. 3. Be a small enough target that nobody makes dancing bunnies for your platform, be happy with being a niche platform.
#1 is what Windows users do, #2 is pretty bad for obvious reasons (and you can't provide an easily accessible developer mode, either, or the dancing bunnies problem will rear its ugly head yet again, by telling the user how to enter developer mode to install the dancing bunnies.) #3 is an acceptable option, but has its downfalls. Closed source driver support, anyone?
CB is rather bandwidth inefficient, though, and can't handle multiple users well. Then again, allowing average Joe to throw up a cell tower isn't the greatest of ideas for spectrum utilization, either.
The monitor? The one used in that shot is a Monitor//c. They're dirt cheap, and if push really comes to shove and you can't find one, or any of the other myriad monochrome composite monitors out there, go to Goodwill and drop $5 or $10 on a TV with composite jacks. Then you even get color for any computers that have the ability to drive a color monitor.
Yeah, Briel's latest products are using Propellers as video chips. Previous revisions of the Replica-1 didn't use a Prop.
There's also the A-One, which IIRC is somewhat more faithful (but still with modern components and compatibility with modern peripherals,) and the Obtronix clone, which is an attempt at an exact replica.
Except that it's not just "implement the spec," partially because, IIRC, "the spec" that's been released to the public is that of Flash 7, which nobody uses any more, and Flash 9 is considered the minimum.
PE doesn't. Now, I think you could have a.NET CLR (or just x86, and emulate on non-x86 platforms, this would just be a stub) stub that called the image for the correct architecture, within the PE format, but I believe it'd need the other images to be in separate files.
I don't want to use the proprietary plugin, but I want to access content that requires that plugin.
And, no, scripts to grab the content manually are not an answer, I want to watch just any Flash video, including streaming ones that have a crapload of keepalives to make it very difficult to use a standalone client, you must use their Flash client. (*cough*UStream*cough*)
What MS could do is change the executable format for Windows 8, to allow for fat binaries, and then make their compilers always compile to x86/Itanium/ARM fat binaries.
(Speaking of that, that's why MS was pushing.NET so hard, because Itanium was supposed to be the future, and MS didn't want to get left behind by CPU architecture changes - hence trying to move everything to interpreted bytecode.)
Not only that, they already have some experience with ARM - some of the Latitudes have an optional instant-on environment that uses an ARM instead of the x86, IIRC.
Slashdot Mirror
Actually, the summary is wrong, they haven't done a thing to the Treo Pro, 800w, 750, 700w/x, or 500v.
They don't run Palm OS, they run Windows Mobile. Then again, I don't know if Mac OS supports ActiveSync...
There actually are apps out there that run as kernel mode drivers and access the RAM that is inaccessible to the OS, giving you a RAMdisk. Said RAMdisk can then be used for swap space. Yes, it sounds horribly ridiculous on the surface, but it does work.
Of course, if you want to get more ridiculous... do a RAID setup of some sort that allows you to start on the RAMdisk, then go to HDD when that's full.
Myself, I'll go for a different approach on my machine with both a 32-bit CPU and a chipset that has a hard 3 GiB limitation - I'm going to install an 8 GiB Mini-PCIe SSD, and either run ReadyBoost, or dedicate it to my swap file.
Actually, MOST consoles. (This'll be US-centric, here.)
Fairchild VES -> Fairchild Channel F System II
Atari VCS -> Atari 2600 Jr.
Mattel Intellivision -> Mattel Intellivision II
Nintendo Entertainment System -> Nintendo NES-101
Sega Master System -> Sega Master System II
Nintendo Game Boy -> Nintendo Game Boy Pocket
Sega Genesis -> Sega Genesis 2 -> Majesco/Sega Genesis 3 (and that's not even counting the Sega Nomad)
Nintendo Super NES -> Nintendo SNS-101
Sony PlayStation -> Sony PSone
Nintendo Game Boy Advance -> Nintendo GBA SP -> Nintendo GB Micro
Sony PlayStation 2 -> Sony Slimline PS2
Nintendo DS -> Nintendo DS Lite
Sony PlayStation 3 -> Sony PS3 Slim
And that list is far from exhaustive. :)
Not when it's a government outside of the jurisdiction of the US government that's doing it...
Also, why would I want to drive such an "underpowered vehicle"?
I can drive my car hard on a public road, and not get arrested for speeding. ;)
Outbraking and outaccelerating are independent.
Anyway, I have seen very few times that people were, in the real world, accelerating faster than my car is capable of. Now, their cars are capable of accelerating faster, yes - my Miata is slower than almost every current minivan, FFS. But I actually press down my accelerator and wind it out to 7000 at times, and they don't.
Not always. See Jack Thompson.
I've got somewhere under 100 hp remaining in my Miata. (Worn out engine, one cylinder is WAY below spec on compression. Started with 116 hp.)
Want to know how I don't get squashed? I actually accelerate. I don't think I've ever had a situation where it was lacking in power, and that's even when a friend drove it in DC traffic. Never had a problem with taking advantage of gaps, and I can break the rear wheels loose in second in a corner, and that's with good tires. (Toyo Proxes T-1Rs, to be specific.)
And, I had a 52 hp Golf diesel. That thing... yes, it was dangerous. How did I not get squashed? I drove like a complete idiot. That car was all about momentum - if you can keep it, you're good. And if you can't keep it, play chicken with the semi truck in the way of merging in, he doesn't want to crash even if it won't be his fault. As for driving on city streets, I never found that to be a problem, because of the torque.
If you can't drive a 100 hp (at the crank) compact car in city traffic, you suck at driving.
The thing is, nobody has a clue on how to actually maintain a VW diesel here, yet they have insanely inflated resale value, so by the time you've bought one and brought it back up to correct levels of maintenance (and a VW that's improperly maintained WILL bite you in the ass, I know this all too well,) you could've bought a cheap gas car and the gasoline to make up the price difference over the lifetime of the car.
Financially, it does not make sense to buy a diesel car in the US, unless you have very, very picky requirements that rule out everything that isn't a VW Golf/Jetta. (A diesel pickup is another story, although while the engine in that Ram may well outlast you with care, the rest of the truck won't.)
However, they use less resources, have longer range, and have various other benefits (mmm, torque,) so there are reasons to buy one.
Pretty sure he's comparing SAE net horsepower with SAE net horsepower of modern cars more than SAE net vs. SAE gross.
Anyway, diesels are the same way about stump-pulling torque, except more so... while being a 4 or 6-cyl. As for the 4/6-cyl "boy racer" comments... there is more than one way to skin a cat, and there is a lot to be said about performance (or economy) through light weight. :) And, there were quite a few 4/6-cyl sports cars back then, too.
IIRC, the VW (it was a VW engine) 1.6 I4/2.0 I5/2.4 I6 indirect injection turbodiesels had 9 PSI of boost. Granted, for a diesel that's not considered much, especially today. But, IIRC, the "Volvo" D24 was 78 hp, versus 102 hp for the D24T that you're referring to.
You're thinking of the later DX block, the original block was, IIRC, identical to the gasoline block.
Very true, but my point was more that the GSM protocol is specifically designed to handle quite a lot of users on one tower, and to keep them from stomping on each other or on other towers by keeping power down, whereas CB users usually blast full power (or even illegally high power.)
A modified GSM (or CDMA, or even AMPS) system would be interesting to see in amateur radio, where one should only use the minimum amount of power necessary to make the contact. Modified because you'd want to remove all billing, you'd want to use callsigns instead of phone numbers (dedicated equipment would be a must, because you'd have to run on amateur frequencies, so changing stuff like that wouldn't be a big issue,) and you'd want to remove the GSM encryption (amateur radio doesn't allow for encryption.)
Want to know the most flawed part of Windows security? Its users.
Both in number and in desire to run applications of their choosing.
Number, because malware writers in 2009 often do it either for the money (directly or indirectly,) or to create a botnet.
Desire to run applications of their choosing because of the dancing bunnies problem.
But, even if you do know how to avoid malware, unless you believe in disassembling every program you use, and studying the disassembly before running the program, and then running it in a machine hooked straight to another machine, both machines separate from your network and the internet, one machine running the malware, one running Wireshark, and reloading the OS, updates, and apps on both after every test run... the dancing bunnies problem is still a problem. The only reason that it's only a problem on Windows is... Windows is the biggest target by FAR. If Linux were a big target, you'd get dancing bunnies problems on Linux.
There are only three REAL solutions to the dancing bunnies problem.
1. Detect the payload - read: antivirus software
2. Require every single application that runs on the platform to go through that sandboxing and testing procedure - read: iPhone, and we all know how well that goes.
3. Be a small enough target that nobody makes dancing bunnies for your platform, be happy with being a niche platform.
#1 is what Windows users do, #2 is pretty bad for obvious reasons (and you can't provide an easily accessible developer mode, either, or the dancing bunnies problem will rear its ugly head yet again, by telling the user how to enter developer mode to install the dancing bunnies.) #3 is an acceptable option, but has its downfalls. Closed source driver support, anyone?
CB is rather bandwidth inefficient, though, and can't handle multiple users well. Then again, allowing average Joe to throw up a cell tower isn't the greatest of ideas for spectrum utilization, either.
The monitor? The one used in that shot is a Monitor //c. They're dirt cheap, and if push really comes to shove and you can't find one, or any of the other myriad monochrome composite monitors out there, go to Goodwill and drop $5 or $10 on a TV with composite jacks. Then you even get color for any computers that have the ability to drive a color monitor.
Done.
http://www.willegal.net/appleii/appleii-recreation.htm
Yeah, Briel's latest products are using Propellers as video chips. Previous revisions of the Replica-1 didn't use a Prop.
There's also the A-One, which IIRC is somewhat more faithful (but still with modern components and compatibility with modern peripherals,) and the Obtronix clone, which is an attempt at an exact replica.
Except that it's not just "implement the spec," partially because, IIRC, "the spec" that's been released to the public is that of Flash 7, which nobody uses any more, and Flash 9 is considered the minimum.
PE doesn't. Now, I think you could have a .NET CLR (or just x86, and emulate on non-x86 platforms, this would just be a stub) stub that called the image for the correct architecture, within the PE format, but I believe it'd need the other images to be in separate files.
Well, on the ARM, you could run Linux + QEMU + WINE, or Linux + QEMU + Windows... but that'd be horribly slow.
I don't want to use the proprietary plugin, but I want to access content that requires that plugin.
And, no, scripts to grab the content manually are not an answer, I want to watch just any Flash video, including streaming ones that have a crapload of keepalives to make it very difficult to use a standalone client, you must use their Flash client. (*cough*UStream*cough*)
What MS could do is change the executable format for Windows 8, to allow for fat binaries, and then make their compilers always compile to x86/Itanium/ARM fat binaries.
(Speaking of that, that's why MS was pushing .NET so hard, because Itanium was supposed to be the future, and MS didn't want to get left behind by CPU architecture changes - hence trying to move everything to interpreted bytecode.)
Not only that, they already have some experience with ARM - some of the Latitudes have an optional instant-on environment that uses an ARM instead of the x86, IIRC.
It has a PowerVR graphics chipset that Intel stuck their label on, not an Intel graphics chipset. No open drivers for that.