Just scale it in the WM. iOS seems to do fine with it. You can either leave it at 1:1 but have a really small screen or double it etc. nVidia drivers can do it, I have a display (projector) that can only output in one format (1400x1050 @ 120Hz). You can put in a 'new' resolution with custom timings. I leave the timings set to the native resolution but the active pixels to 640x480, 800x600 and 1024x768 - scales it really nicely to my set resolution.
I think the problem is that the people at the polling offices and republicans keep repeating the phrase that "if you have no ID we can't make sure you're not committing voter fraud" - they try to make it so that not having ID is voter fraud in itself. Having such signs in front combined with the right-wing media and right-wing officials even though no laws have been in place is indeed intimidation.
No I don't remember them because MS never really made hardware themselves before the XBox. The keyboards, mice and joysticks were made by Logitech and simply rebadged just as Dell and a host of other companies did. This is a blatant case of astroturfing.
The rated lifespan for a CFL is ~6,000-15,000 hours (1 year if you left it continuously on). Much better than incandescents but not nearly as good as LED that have a 20-30 year lifespan (if you left it continuously on).
Also CFL's have all kinds of nasty side effects like mercury and other gasses inside the bulb, leave a really dirty signature on the net and have a really bad power factor. They're fluorescent tubes after all except where you could've gotten a decent ballast with a good coil on the big things, the designers of CFL tubes have all but stripped everything but a cheap electrolyte capacitor (which blows it's guts the moment the net browns out) and a badly coiled piece of wire (which is usually smashed during assembly to fit it in the base).
Besides that, the flickering on that thing (50 or 60Hz depending on your location) gives many a headache and screws with fast shutter speeds on camera's.
Not to rain on your parade, but the SonicWall's are really just D-Link routers running a re-badged version of Linux (you can even drop to the command line and inspect iptables) while most of the shit Dell and HP churns out is not much better than the TigerDirect special.
I myself buy Netgear's ProSafe stuff for the network because it does the same stuff and has the same capabilities as Cisco etc. but for about 1/10th the price and most of my servers are SuperMicro because the first time I bought a COTS server, it was a rebadged SuperMicro server with a 50% premium. Off course, I don't use Windows so I have no problems with drivers and my desktops are Mac's so I barely have to touch the machines after they've been imaged, if it breaks, I troubleshoot and after 5 minutes on the phone Apple sends a tech out which is way better than the Dell Gold contract I inherited during the "we're not responsible for those blown caps" and the "call nVidia if your GPU blows up" debacles where I had to replace 10's of motherboards myself or have all my people without computer as I send them all in and wait 3 weeks for repairs.
Yes, you could end up with an awesome solution but you would have to hire a really good project lead and programmers that know what they are doing. Given the quality of medical software I have seen so far, the so-called cream-of-the-crop that have actually worked on some of those things couldn't program their way out of a box using Logo.
Yeah, you wish that would happen. I work in the reality. 100k patient records potentially on the street and the 'fine' was not even close to $1M which included the lawyers' cost and the bogus ID protection service that continuously up-sells their own services. They just wrote it off as the cost of doing business, gave everyone involved in the breach a seminar on it and a couple of mea-culpa's from the CIO.
Yeah, if you're implementing your EHR/EMR that way, all your records will be unavailable at the first snag you hit which on a centralized system can be many (single point of failure becomes the farm, data centers, the (wireless and wired) networks, the software, Windows Update...)
EHR/EMR in REAL hospitals is implemented by having read-only copies of relevant databases stored on key workstations in areas and have full records for patients and special cases in the area on individual workstations, bedside computer units, head nurse's iPad's and doctor's iPhone's.
You will be using less bandwidth and thus the spectrum will be cleaner but you will still be 'stomping' on the neighbors but only slightly less. Your broadcast system will still have to negotiate (using CTS/RTS signals) but now slightly less much.
So your bandwidth MAY become more stable but at a lower rate while than if you leave it at auto-negotiate, your bandwidth will fluctuate as your neighbors are more or less active. Which is better is for you and your application (a stable 6Mbps or between 6 and 11Mbps fluctuation) to decide. Things like Netflix for example automatically negotiate the quality depending on available throughput based on the fluctuation of bandwidth over longer periods of time however those algorithms could have issues with fast fluctuations.
The best solution to having your neighbors not stomp YOU out is to have the stronger antenna or use a free and clear channel, get a better router with better antenna's. I have noticed that routers $150 are typically pretty shitty, then you go into the business ones and they give good quality and options.
If you can drive the signal up, your SNR will improve and thus the quality of YOUR connection while their noise floor goes up.
What else you could also do is convert your house or living unit into a Faraday cage which may be somewhat expensive. Another (somewhat illegal) solution is to use a firmware like DD-WRT and set the channel or the antenna (if possible on your hardware) to a channel that isn't allowed to be used in your country like 14 - you can be pretty sure it will be clear and free, and if all your gear supports it even at a low setting you may get acceptable quality out of it. Just don't get caught doing it. Another (somewhat illegal) solution is to set all the Linksys and Netgear SSID's to channel 1 while you use the other end of the spectrum. Another (somewhat awkward) solution is to contact your closest neighbors (as they create the most noise) and see if you can't negotiate on which channels to use. However the 5GHz band is pretty much open these days (although it will get cluttered again in a couple of years as 2.4 is right now) and there must be some other bands that you can use so make your own transmitter at a licensed-for-tinkering spectrum and have at it.
The problem is that 3 is overlapping both 1 and 6 channels so if they're extremely busy, you'll end up waiting on clearance (as your transmissions will be colliding) in both channels before your transmission is successful.
The reason 1 and 6 are 'safe' is because besides a certain center frequency they also have a bandwidth (a frequency space to the left and right) which tapers off as you go away from the center frequency. You may know that bandwidth is related to the amount of data (bitrate) you can send (see Hartley's Law for further research).
3 overlaps both 1 and 6's bandwidth so activity on either band will impact the usable spectrum in channel 3. Sure it will still work well but you may have a higher rate of collisions depending on the activity in either band.
Also, filters and antenna's aren't perfect and the cheaper the device gets, the cheaper and as a result worse the filter and antenna design is and also the worse the handling of the unused signal is (and at some point those designers don't actually care about the rest of the spectrum, harmonics etc). So if the middle of the channel you use is on the edges of another channel (or it's harmonics) it may be very noisy there.
You don't need UEFI for that. Just put in a semi-recent SATA controller and WinXP installers choke on it. UEFI is to keep home-brew and FOSS out, they couldn't care less if you got XP to run on it.
GE: Linux 2.2 and Sun Solaris 7 (not kidding, I have to keep resuscitating a Sun SPARCstation 20 just so we can compile crap for the GE scanner) Philips: WinNT and XP Fujitsu: Home brew unix-like system
The lawsuits and associated costs are minimal compared to some overhauls.
Lawsuit settled with a couple of identity protection services: $2M Overhauling all software to run on the latest platforms and implement e-records: $50M Having no tech specs nor existing companies to support the software you just implemented and have history repeat itself every decade: Priceless
100B is 0.1 Trillion for a country the same size of the US. Compare that to the military budget of either country and you should see that the problem is not necessarily cost of the project, it's the will power of the governments to invest in it.
That is one of the big myths surrounding DC vs. AC.
These days (with solid state components etc.) it's really easy to transfer HVDC over long distances and step-down that voltage to usable power either on AC or DC without needing to synchronize grids, worrying about the skin effect or capacitance losses. HVDC is actually more efficient and cost-effective and used for practically all new high voltage designs these days.
Back in the day (before the early 1960's) AC was indeed more 'easy' to deploy as transformers (spools of wire) are freaking cheap although the losses are significant. But HVAC also introduces the skin effect for high voltage and has the problem that transformers (an RC network) introduces phase shifts while requiring multiple HVAC networks to be synchronized before additional capacity can be generated or require really, really expensive and lossy synchronizers (basically AC->DC->AC converters)
It seems the best way to make corporations comply is to have rules that have teeth. Regardless of what you're going to implement, if you're not planning on executing it, it doesn't matter.
There are rules, enforce them. If it's not enough, make the whole foodchain (corporations that advertise and service providers that do the dirty work ) that supplies such robocalls pay for it - 10% of their yearly income to begin with and $1,000 per call.
Really? You must've never heard of Bash, PHP, Perl and a host of other cross-platform (even Windows/Unix) scripting languages that are way more powerful than VB.
It's that attitude (I can build this sh!t in 5 minutes!) that makes for vulnerable (usually commercial, closed source) code that can be easily exploited.
With the current progressions in e-records it's nigh impossible to do what you describe.
a) Data needs to remain available even when the network is down b) Data needs to be available to all manner of portable and remote devices from iPhone's and iPad's to local workstations, remote workstations, remote diagnostics, vendors and contractors troubleshooting and shared to other institutions. c) Everything you push things through can and will at some point crash, need upgrades and need replacement. d) The more devices you add to 'secure' things, the more of a spaghetti it becomes making management extremely hard and holes even bigger.
I work in the industry, it's a touch nut to crack. The problem is that Windows is simply not built for these environments and cannot be adequately secured against threats. There is no SEWindows, there are no RBAC policies that you can apply (and don't get me started on "AD Group Policy" - it's a joke compared to Solaris or SELinux even if you can get all your Windows devices in the AD to begin with) and it's so freaking hard to actually DO anything on the platform from a central location without requiring arcane incantations of a goop between.NET and VB and that's IF you even have something like PowerShell available (which a usable shell in Windows is only a very recent invention)
Why? I don't understand why datacenters need to be hyper-secure from physical entry.
- It's far easier to get in through the electronics of a datacenter - It's far more lucrative to get in through the electronics of a datacenter (how much will you really load up in a truck during a heist?) - The only thing you'd be guaranteed is some cheap hardware you probably can't resell anyway, the servers themselves are probably encrypted.
Besides number 5, all of those are exploitable. It just takes a strong enough light/sound/electromagnetic pulse. See Bluetooth 'sniper' rifles or modified (tin can) WiFi access points. Even though BT only works in the distance of couple of feet, with a strong enough antenna this can be extended to several hundred. Same goes for WiFi.
The thing is that it needs some sort of authentication before letting anyone 'reprogram' you which is severely lacking in these products.
Bigger chips create more heat, that's why we want ever smaller chip processes because they create less heat and thus more stuff can be crammed for the same power requirements. Also, the faster you go the shorter you want the wires to be as eventually you'll become limited by reflections and capacitance of longer wiring.
I think after they analyzed a bunch of RMA's they might have probed for similarities stored in the EEPROM. Then you just set the counter to the value with a production model to test.
I know how they work, I meant by 'unused' that that portion isn't reported to the OS. You can buy 3 physically similar drives from the same vendor and chipset (maybe different types of memory chips) and they will report 100GB (Enterprise, usually SLC or eMLC), 120GB (Mid-level) and 128GB (Cheap) with the same number of chips and identical controllers (although the enterprise may have a gold capacitor soldered on the board)
The ultra-cheap SSD's in my severs lasted only 3 months. The 4 OCZ Vertex 3 IOPS have so far lasted over a year with ~2TB processed per disk, 2 Intel SLC and 2 MLC's already over 2 years over which time they have processed ~10TB each (those were all enterprise grade or close to it). They are in a 60TB array doing caching so they regularly get read/write/deleted. I have some OCZ Talos (SAS) as well where one was DoA and another early-death but simply shipping them into RMA and I had another one in a couple of days. But the rest of them do well over 6 months and going.
Several other random ones still work fine in random desktop machines and workstations.
As far as spare room on those devices, depending on the manufacturing process you get between 5 and 20% unused space where 'bad' blocks come to live. I haven't had one with bad blocks so most of mine have gone out with a bang, usually they just stop responding and drop out, totally dead. I would definitely recommend RAID6 or mirrors as they do die just like normal hard drives (I just had 3 identical 3TB drives die in the last week)
Slashdot Mirror
Just scale it in the WM. iOS seems to do fine with it. You can either leave it at 1:1 but have a really small screen or double it etc. nVidia drivers can do it, I have a display (projector) that can only output in one format (1400x1050 @ 120Hz). You can put in a 'new' resolution with custom timings. I leave the timings set to the native resolution but the active pixels to 640x480, 800x600 and 1024x768 - scales it really nicely to my set resolution.
I think the problem is that the people at the polling offices and republicans keep repeating the phrase that "if you have no ID we can't make sure you're not committing voter fraud" - they try to make it so that not having ID is voter fraud in itself. Having such signs in front combined with the right-wing media and right-wing officials even though no laws have been in place is indeed intimidation.
No I don't remember them because MS never really made hardware themselves before the XBox. The keyboards, mice and joysticks were made by Logitech and simply rebadged just as Dell and a host of other companies did. This is a blatant case of astroturfing.
The rated lifespan for a CFL is ~6,000-15,000 hours (1 year if you left it continuously on). Much better than incandescents but not nearly as good as LED that have a 20-30 year lifespan (if you left it continuously on).
Also CFL's have all kinds of nasty side effects like mercury and other gasses inside the bulb, leave a really dirty signature on the net and have a really bad power factor. They're fluorescent tubes after all except where you could've gotten a decent ballast with a good coil on the big things, the designers of CFL tubes have all but stripped everything but a cheap electrolyte capacitor (which blows it's guts the moment the net browns out) and a badly coiled piece of wire (which is usually smashed during assembly to fit it in the base).
Besides that, the flickering on that thing (50 or 60Hz depending on your location) gives many a headache and screws with fast shutter speeds on camera's.
Not to rain on your parade, but the SonicWall's are really just D-Link routers running a re-badged version of Linux (you can even drop to the command line and inspect iptables) while most of the shit Dell and HP churns out is not much better than the TigerDirect special.
I myself buy Netgear's ProSafe stuff for the network because it does the same stuff and has the same capabilities as Cisco etc. but for about 1/10th the price and most of my servers are SuperMicro because the first time I bought a COTS server, it was a rebadged SuperMicro server with a 50% premium. Off course, I don't use Windows so I have no problems with drivers and my desktops are Mac's so I barely have to touch the machines after they've been imaged, if it breaks, I troubleshoot and after 5 minutes on the phone Apple sends a tech out which is way better than the Dell Gold contract I inherited during the "we're not responsible for those blown caps" and the "call nVidia if your GPU blows up" debacles where I had to replace 10's of motherboards myself or have all my people without computer as I send them all in and wait 3 weeks for repairs.
Yes, you could end up with an awesome solution but you would have to hire a really good project lead and programmers that know what they are doing. Given the quality of medical software I have seen so far, the so-called cream-of-the-crop that have actually worked on some of those things couldn't program their way out of a box using Logo.
Yeah, you wish that would happen. I work in the reality. 100k patient records potentially on the street and the 'fine' was not even close to $1M which included the lawyers' cost and the bogus ID protection service that continuously up-sells their own services. They just wrote it off as the cost of doing business, gave everyone involved in the breach a seminar on it and a couple of mea-culpa's from the CIO.
Yeah, if you're implementing your EHR/EMR that way, all your records will be unavailable at the first snag you hit which on a centralized system can be many (single point of failure becomes the farm, data centers, the (wireless and wired) networks, the software, Windows Update ...)
EHR/EMR in REAL hospitals is implemented by having read-only copies of relevant databases stored on key workstations in areas and have full records for patients and special cases in the area on individual workstations, bedside computer units, head nurse's iPad's and doctor's iPhone's.
You will be using less bandwidth and thus the spectrum will be cleaner but you will still be 'stomping' on the neighbors but only slightly less. Your broadcast system will still have to negotiate (using CTS/RTS signals) but now slightly less much.
So your bandwidth MAY become more stable but at a lower rate while than if you leave it at auto-negotiate, your bandwidth will fluctuate as your neighbors are more or less active. Which is better is for you and your application (a stable 6Mbps or between 6 and 11Mbps fluctuation) to decide. Things like Netflix for example automatically negotiate the quality depending on available throughput based on the fluctuation of bandwidth over longer periods of time however those algorithms could have issues with fast fluctuations.
The best solution to having your neighbors not stomp YOU out is to have the stronger antenna or use a free and clear channel, get a better router with better antenna's. I have noticed that routers $150 are typically pretty shitty, then you go into the business ones and they give good quality and options.
If you can drive the signal up, your SNR will improve and thus the quality of YOUR connection while their noise floor goes up.
What else you could also do is convert your house or living unit into a Faraday cage which may be somewhat expensive. Another (somewhat illegal) solution is to use a firmware like DD-WRT and set the channel or the antenna (if possible on your hardware) to a channel that isn't allowed to be used in your country like 14 - you can be pretty sure it will be clear and free, and if all your gear supports it even at a low setting you may get acceptable quality out of it. Just don't get caught doing it. Another (somewhat illegal) solution is to set all the Linksys and Netgear SSID's to channel 1 while you use the other end of the spectrum. Another (somewhat awkward) solution is to contact your closest neighbors (as they create the most noise) and see if you can't negotiate on which channels to use. However the 5GHz band is pretty much open these days (although it will get cluttered again in a couple of years as 2.4 is right now) and there must be some other bands that you can use so make your own transmitter at a licensed-for-tinkering spectrum and have at it.
The problem is that 3 is overlapping both 1 and 6 channels so if they're extremely busy, you'll end up waiting on clearance (as your transmissions will be colliding) in both channels before your transmission is successful.
The reason 1 and 6 are 'safe' is because besides a certain center frequency they also have a bandwidth (a frequency space to the left and right) which tapers off as you go away from the center frequency. You may know that bandwidth is related to the amount of data (bitrate) you can send (see Hartley's Law for further research).
3 overlaps both 1 and 6's bandwidth so activity on either band will impact the usable spectrum in channel 3. Sure it will still work well but you may have a higher rate of collisions depending on the activity in either band.
Also, filters and antenna's aren't perfect and the cheaper the device gets, the cheaper and as a result worse the filter and antenna design is and also the worse the handling of the unused signal is (and at some point those designers don't actually care about the rest of the spectrum, harmonics etc). So if the middle of the channel you use is on the edges of another channel (or it's harmonics) it may be very noisy there.
You don't need UEFI for that. Just put in a semi-recent SATA controller and WinXP installers choke on it. UEFI is to keep home-brew and FOSS out, they couldn't care less if you got XP to run on it.
So what would you go with?
GE: Linux 2.2 and Sun Solaris 7 (not kidding, I have to keep resuscitating a Sun SPARCstation 20 just so we can compile crap for the GE scanner)
Philips: WinNT and XP
Fujitsu: Home brew unix-like system
The lawsuits and associated costs are minimal compared to some overhauls.
Lawsuit settled with a couple of identity protection services: $2M
Overhauling all software to run on the latest platforms and implement e-records: $50M
Having no tech specs nor existing companies to support the software you just implemented and have history repeat itself every decade: Priceless
100B is 0.1 Trillion for a country the same size of the US. Compare that to the military budget of either country and you should see that the problem is not necessarily cost of the project, it's the will power of the governments to invest in it.
That is one of the big myths surrounding DC vs. AC.
These days (with solid state components etc.) it's really easy to transfer HVDC over long distances and step-down that voltage to usable power either on AC or DC without needing to synchronize grids, worrying about the skin effect or capacitance losses. HVDC is actually more efficient and cost-effective and used for practically all new high voltage designs these days.
Back in the day (before the early 1960's) AC was indeed more 'easy' to deploy as transformers (spools of wire) are freaking cheap although the losses are significant. But HVAC also introduces the skin effect for high voltage and has the problem that transformers (an RC network) introduces phase shifts while requiring multiple HVAC networks to be synchronized before additional capacity can be generated or require really, really expensive and lossy synchronizers (basically AC->DC->AC converters)
It seems the best way to make corporations comply is to have rules that have teeth. Regardless of what you're going to implement, if you're not planning on executing it, it doesn't matter.
There are rules, enforce them. If it's not enough, make the whole foodchain (corporations that advertise and service providers that do the dirty work ) that supplies such robocalls pay for it - 10% of their yearly income to begin with and $1,000 per call.
Really? You must've never heard of Bash, PHP, Perl and a host of other cross-platform (even Windows/Unix) scripting languages that are way more powerful than VB.
It's that attitude (I can build this sh!t in 5 minutes!) that makes for vulnerable (usually commercial, closed source) code that can be easily exploited.
With the current progressions in e-records it's nigh impossible to do what you describe.
a) Data needs to remain available even when the network is down
b) Data needs to be available to all manner of portable and remote devices from iPhone's and iPad's to local workstations, remote workstations, remote diagnostics, vendors and contractors troubleshooting and shared to other institutions.
c) Everything you push things through can and will at some point crash, need upgrades and need replacement.
d) The more devices you add to 'secure' things, the more of a spaghetti it becomes making management extremely hard and holes even bigger.
I work in the industry, it's a touch nut to crack. The problem is that Windows is simply not built for these environments and cannot be adequately secured against threats. There is no SEWindows, there are no RBAC policies that you can apply (and don't get me started on "AD Group Policy" - it's a joke compared to Solaris or SELinux even if you can get all your Windows devices in the AD to begin with) and it's so freaking hard to actually DO anything on the platform from a central location without requiring arcane incantations of a goop between .NET and VB and that's IF you even have something like PowerShell available (which a usable shell in Windows is only a very recent invention)
Why? I don't understand why datacenters need to be hyper-secure from physical entry.
- It's far easier to get in through the electronics of a datacenter
- It's far more lucrative to get in through the electronics of a datacenter (how much will you really load up in a truck during a heist?)
- The only thing you'd be guaranteed is some cheap hardware you probably can't resell anyway, the servers themselves are probably encrypted.
Besides number 5, all of those are exploitable. It just takes a strong enough light/sound/electromagnetic pulse. See Bluetooth 'sniper' rifles or modified (tin can) WiFi access points. Even though BT only works in the distance of couple of feet, with a strong enough antenna this can be extended to several hundred. Same goes for WiFi.
The thing is that it needs some sort of authentication before letting anyone 'reprogram' you which is severely lacking in these products.
Bigger chips create more heat, that's why we want ever smaller chip processes because they create less heat and thus more stuff can be crammed for the same power requirements. Also, the faster you go the shorter you want the wires to be as eventually you'll become limited by reflections and capacitance of longer wiring.
I think after they analyzed a bunch of RMA's they might have probed for similarities stored in the EEPROM. Then you just set the counter to the value with a production model to test.
I know how they work, I meant by 'unused' that that portion isn't reported to the OS. You can buy 3 physically similar drives from the same vendor and chipset (maybe different types of memory chips) and they will report 100GB (Enterprise, usually SLC or eMLC), 120GB (Mid-level) and 128GB (Cheap) with the same number of chips and identical controllers (although the enterprise may have a gold capacitor soldered on the board)
The ultra-cheap SSD's in my severs lasted only 3 months. The 4 OCZ Vertex 3 IOPS have so far lasted over a year with ~2TB processed per disk, 2 Intel SLC and 2 MLC's already over 2 years over which time they have processed ~10TB each (those were all enterprise grade or close to it). They are in a 60TB array doing caching so they regularly get read/write/deleted. I have some OCZ Talos (SAS) as well where one was DoA and another early-death but simply shipping them into RMA and I had another one in a couple of days. But the rest of them do well over 6 months and going.
Several other random ones still work fine in random desktop machines and workstations.
As far as spare room on those devices, depending on the manufacturing process you get between 5 and 20% unused space where 'bad' blocks come to live. I haven't had one with bad blocks so most of mine have gone out with a bang, usually they just stop responding and drop out, totally dead. I would definitely recommend RAID6 or mirrors as they do die just like normal hard drives (I just had 3 identical 3TB drives die in the last week)
Read up on the history of fluoride and how they decided it needed to be added it to the water. There has been to date no FDA review of this practice.