That was just one limited series of bad drives from IBM. Thats nothing in the long run if you compare all the way back to 1.0G and smaller drives. Maxtor has by far had the most troubled drives of the big players, but Seagate and WD have both had their share of bad runs of drives. Don't even get started on Samsung, Fujitsu, Conner(bought by Seagate), Quantum(bought by Maxtor), Toshiba, NEC, etc. Overall, I wouldn't buy anything but Hitachi and maybe Seagate drives, unless I didn't value my data.
Left arrow moves you (the viewer) left, and the map thus moves right. Wheel up moves you closer down to the surface, and thus should zoom in.
The most common 3D interface people are used to is going to be from any 3D FPS games, which work exactly the same way. Wheel up = zoom in (think any sniper rifle).
I've used some game development related 3D programs a little bit, and some that supported the mouse wheel also used wheel up = zoom in.
With Jabber, aren't you saying that you have two accounts logged into two servers, with one program then? I still use the ICQ client (2003b) and I can add AIM screennames to my list just fine. No problems chatting with AIM people at all. I can also log into iChat on my test OSX box with my ICQ number, and it works all the same from there. The only major issue is certain client-side functionality is different between people using ICQ and AIM, but thats the client, not the networks fault. Point being here, AOL likely had to do nothing special to include both ICQ numbers and AOL screennames in the 3rd degree of friends searches, so ICQ numbers work just fine in the AIMFight.
Buddy lists are stored on the main AIM server, so it probably doesn't matter if anybody is signed in or not. You are still on peoples lists and people are still on your list, even if your computer is off.
AIM screennames are unique strings, while ICQ has unique numbers. You can enter ICQ numbers in the AIMFight tool it looks like, but entering a string would be looking for the AIM screenname. AIM and ICQ are basically the same network now, and since the unique ID for ICQ is a number, most AIM clients only show that number as your screenname, ignoring the nickname you can attach to your ICQ number.
I'm pretty sure ICQ and AIM are more or less the same now. You can log into just about any AIM client with your ICQ number as the screenname, and the same password. You can add ICQ people to your AIM buddy list and AIM people to your ICQ list. You can compare two ICQ numbers using that AIMFight tool, so I assume it does follow the list of buddy connections for both networks when adding up the numbers.
Pentium 90s and 100s where just coming out when I got my Am486DX4-100 CPU, so I can believe it. The first generation pentiums (which was just the 60s and 66s) where a bit older and clunkier then the 75s and up. Most of my computers before that 486 probably did honor the turbo pin. The 486's motherboard manual actually listed the keyboard combination which was hard-coded into the BIOS, saying that the turbo pins where not connected.
Turning it off on some OLD computers would actually downclock it to 4.77MHz to run programs that assumed timing of the original XT. Newer computers (486, early pentium) BIOSes ignored the hardware turbo pin and left the CPU at full speed at all time, except some had hard-coded shortcut keys such as my 486DX4-100 machine which had CTRL+ALT+PGDN to disable turbo, and CTRL+ALT+PGUP to re-enable it. You sure could notice if you where playing Doom and turned turbo off: Super slow mode!
Generally, the best way to ensure that some style is only applied to IE5.5/IE6.0 is to use a supported hack, not just some trick hack that may be fixed in the future. For example:
This kind of web design will always assume that IE 7.0 becomes fixed to work like the standard, but you can always change the test to "lte ie 7.0" instead of "lte ie 6.0" if needed.
The page you link to, titled "How is a plane protected from Lightning strikes?" references a page "Wingtips by The 737 Technical Site", which says about the static wicks: Note that they are not for lightning protection.
So, I am a little confused here. They obviously stop some smaller charge build-ups, but what about the lightning issue? Yes or no, and if no, what does protect an airplain from lightning, other then not flying into a storm?
240 internally, but 224 externally on NTSC, so 224 is what really matters. I don't know if the extra 8 pixels on the top and bottom are actually possible to see or not, if you adjust your TV to shrink the image vertically. I assume they are not.
NES and SNES where both 256x224, although SNES supported 512x448, it was only used for some still screens usually, not any action in-game. It's the 8x8 tile which is only allowed 4 colors per tile (on NES) that really creates the bad graphics. Allowing truecolor sprites and backgrounds, and taking advantage of that, even at 256x224, would make the games look a ton better probably.
They still don't show exit numbers on freeway exits, which would be really useful. Of course, a scale would be really helpful too, so I know how long a mile or km is supposed to be at a given zoom level and map distortion.
Of course, the CC companies DON'T CARE if you are trying to get some free stuff. They will happily issue chargebacks and give you your money back. The only person hurt here is the merchant, who loses the amount of the sale, a transaction fee of a few percent of the sale price in both directions (one for the sale, one for the chargeback), and a chargeback fee of at least $35 per item being forcefully refunded.
So as you can see, it is the merchants that people are abusing, not the CC companies. The CC companies pocket the chargeback fee as well as double the transaction fees, without having to pay out a cent to the merchant. The customer gets their free item and all of their money back, and the merchant is out one item and probably $40 or more, depending on that items cost.
I'm not suggesting that people should withhold from reporting fraudulant use of their cards, but it is easy for people to get away with stealing from merchants, and neither the theifs taking the CC numbers, nor the people abusing the situation and getting free stuff are hurting the CC companies at all.
I think the law makes it seem like it's possible to be sharing material between two customers of an ISP, either by running a webserver or some other means. This means that the ISP must filter in both directions, and could maybe give them power to search their customers computers to ensure no outbound "harmful" material is allowed. I'm not really sure here if thats what the original poster meant, but it might be.
No, let me tell you, I've lived in both WI and MI, and WI does not have lake effect snow. The wind just does not blow that way. There is a ton more snow in MI, especially on the west coast of MI, not that it is anything to brag about really. Long winters and short summers suck.
As a programmer, I still have a harder time caring about OSX compared to Windows and Linux, mainly because of Objective C. Since I am trying to make a living programming, I don't always do open source programs though, and the ones I intend to sell for profit will likely only have a Windows and OSX version, because there isn't much market for buying software for Linux yet. When writing something for free, I tend to only write for Windows and Linux, since it requires minimal extra effort to make 1 program compile for both. I don't see how OSX on x86 really changed anything here. Commercial software will still target OSX part of the time, and free software will stil target Linux part of the time.
You can mix them, sure, thats what I do now. I divide the application into two pieces, sorta like a Model / View separation, with as much code as possible in the Model. The core "Model" is a static lib written in C++ and is cross-platform, standard code, which can compile under Visual Studio, or gcc on Linux/OSX with a Makefile. The GUI is then written as a thin shell on top of that, in MFC/C++ for Windows , and Cocoa/ObjC for OSX. It is much easier to write the Windows GUI, and easier to keep track of since it uses the same language as the core library. What I want is to be able to write the entire OSX GUI in C++, instead of ObjC, and still use Cocoa. I doubt that is going to happen, and ObjectiveC is really a pain in the ass for us compared to C++, to the point where some programs we just don't bother to spend the extra time making OSX versions for.
Even if the chipset is locked down, simply using a little endian instead of big endian will make a world of difference with windows compatibility. Now, if only they could support C++ with Cocoa, because I would rather go back and program in BASIC then use that horrible backwards of a language "Objective C".
When slipstreaming a SP into Windows 2000 or XP, I've just used "Bart's Boot Image Extractor" (bbie.exe) to extract the boot sectory from the original CD, and burned a bootable CD with Nero. It works just fine.
Slashdot Mirror
That was just one limited series of bad drives from IBM. Thats nothing in the long run if you compare all the way back to 1.0G and smaller drives. Maxtor has by far had the most troubled drives of the big players, but Seagate and WD have both had their share of bad runs of drives. Don't even get started on Samsung, Fujitsu, Conner(bought by Seagate), Quantum(bought by Maxtor), Toshiba, NEC, etc. Overall, I wouldn't buy anything but Hitachi and maybe Seagate drives, unless I didn't value my data.
Wheel up = zoom in, anything else is wrong.
Left arrow moves you (the viewer) left, and the map thus moves right. Wheel up moves you closer down to the surface, and thus should zoom in.
The most common 3D interface people are used to is going to be from any 3D FPS games, which work exactly the same way. Wheel up = zoom in (think any sniper rifle).
I've used some game development related 3D programs a little bit, and some that supported the mouse wheel also used wheel up = zoom in.
Still NO EXIT NUMBERS!
I can't believe I still use Mapquest's tiny and slow interface just to find freeway exit numbers.
With Jabber, aren't you saying that you have two accounts logged into two servers, with one program then? I still use the ICQ client (2003b) and I can add AIM screennames to my list just fine. No problems chatting with AIM people at all. I can also log into iChat on my test OSX box with my ICQ number, and it works all the same from there. The only major issue is certain client-side functionality is different between people using ICQ and AIM, but thats the client, not the networks fault. Point being here, AOL likely had to do nothing special to include both ICQ numbers and AOL screennames in the 3rd degree of friends searches, so ICQ numbers work just fine in the AIMFight.
Buddy lists are stored on the main AIM server, so it probably doesn't matter if anybody is signed in or not. You are still on peoples lists and people are still on your list, even if your computer is off.
AIM screennames are unique strings, while ICQ has unique numbers. You can enter ICQ numbers in the AIMFight tool it looks like, but entering a string would be looking for the AIM screenname. AIM and ICQ are basically the same network now, and since the unique ID for ICQ is a number, most AIM clients only show that number as your screenname, ignoring the nickname you can attach to your ICQ number.
I'm pretty sure ICQ and AIM are more or less the same now. You can log into just about any AIM client with your ICQ number as the screenname, and the same password. You can add ICQ people to your AIM buddy list and AIM people to your ICQ list. You can compare two ICQ numbers using that AIMFight tool, so I assume it does follow the list of buddy connections for both networks when adding up the numbers.
Pentium 90s and 100s where just coming out when I got my Am486DX4-100 CPU, so I can believe it. The first generation pentiums (which was just the 60s and 66s) where a bit older and clunkier then the 75s and up. Most of my computers before that 486 probably did honor the turbo pin. The 486's motherboard manual actually listed the keyboard combination which was hard-coded into the BIOS, saying that the turbo pins where not connected.
Turning it off on some OLD computers would actually downclock it to 4.77MHz to run programs that assumed timing of the original XT. Newer computers (486, early pentium) BIOSes ignored the hardware turbo pin and left the CPU at full speed at all time, except some had hard-coded shortcut keys such as my 486DX4-100 machine which had CTRL+ALT+PGDN to disable turbo, and CTRL+ALT+PGUP to re-enable it. You sure could notice if you where playing Doom and turned turbo off: Super slow mode!
Generally, the best way to ensure that some style is only applied to IE5.5/IE6.0 is to use a supported hack, not just some trick hack that may be fixed in the future. For example:
.75; }
<style type="text/css">
#someid { opacity:
</style>
<!--[if gte ie 5.5]><![if lte ie 6.0]>
<style type="text/css">
#someid { filter: alpha(opacity=75); }
</style>
<![endif]><![endif]-->
This kind of web design will always assume that IE 7.0 becomes fixed to work like the standard, but you can always change the test to "lte ie 7.0" instead of "lte ie 6.0" if needed.
The page you link to, titled "How is a plane protected from Lightning strikes?" references a page "Wingtips by The 737 Technical Site", which says about the static wicks: Note that they are not for lightning protection.
So, I am a little confused here. They obviously stop some smaller charge build-ups, but what about the lightning issue? Yes or no, and if no, what does protect an airplain from lightning, other then not flying into a storm?
240 internally, but 224 externally on NTSC, so 224 is what really matters. I don't know if the extra 8 pixels on the top and bottom are actually possible to see or not, if you adjust your TV to shrink the image vertically. I assume they are not.
NES and SNES where both 256x224, although SNES supported 512x448, it was only used for some still screens usually, not any action in-game.
It's the 8x8 tile which is only allowed 4 colors per tile (on NES) that really creates the bad graphics. Allowing truecolor sprites and backgrounds, and taking advantage of that, even at 256x224, would make the games look a ton better probably.
CAkin to MFC as a framework, with Win32 as an API, using C++ as a language.
They still don't show exit numbers on freeway exits, which would be really useful. Of course, a scale would be really helpful too, so I know how long a mile or km is supposed to be at a given zoom level and map distortion.
Of course, the CC companies DON'T CARE if you are trying to get some free stuff. They will happily issue chargebacks and give you your money back. The only person hurt here is the merchant, who loses the amount of the sale, a transaction fee of a few percent of the sale price in both directions (one for the sale, one for the chargeback), and a chargeback fee of at least $35 per item being forcefully refunded.
So as you can see, it is the merchants that people are abusing, not the CC companies. The CC companies pocket the chargeback fee as well as double the transaction fees, without having to pay out a cent to the merchant. The customer gets their free item and all of their money back, and the merchant is out one item and probably $40 or more, depending on that items cost.
I'm not suggesting that people should withhold from reporting fraudulant use of their cards, but it is easy for people to get away with stealing from merchants, and neither the theifs taking the CC numbers, nor the people abusing the situation and getting free stuff are hurting the CC companies at all.
It's also pretty annoying to fast forward a DVD when the stupid thing just puts up a big red X icon and forces you to watch crap you don't care about.
I think the law makes it seem like it's possible to be sharing material between two customers of an ISP, either by running a webserver or some other means. This means that the ISP must filter in both directions, and could maybe give them power to search their customers computers to ensure no outbound "harmful" material is allowed. I'm not really sure here if thats what the original poster meant, but it might be.
No, let me tell you, I've lived in both WI and MI, and WI does not have lake effect snow. The wind just does not blow that way. There is a ton more snow in MI, especially on the west coast of MI, not that it is anything to brag about really. Long winters and short summers suck.
It can still be right, at midnight and noon, for alternating portions of those full minutes.
As a programmer, I still have a harder time caring about OSX compared to Windows and Linux, mainly because of Objective C. Since I am trying to make a living programming, I don't always do open source programs though, and the ones I intend to sell for profit will likely only have a Windows and OSX version, because there isn't much market for buying software for Linux yet. When writing something for free, I tend to only write for Windows and Linux, since it requires minimal extra effort to make 1 program compile for both.
I don't see how OSX on x86 really changed anything here. Commercial software will still target OSX part of the time, and free software will stil target Linux part of the time.
You can mix them, sure, thats what I do now. I divide the application into two pieces, sorta like a Model / View separation, with as much code as possible in the Model. The core "Model" is a static lib written in C++ and is cross-platform, standard code, which can compile under Visual Studio, or gcc on Linux/OSX with a Makefile. The GUI is then written as a thin shell on top of that, in MFC/C++ for Windows , and Cocoa/ObjC for OSX. It is much easier to write the Windows GUI, and easier to keep track of since it uses the same language as the core library.
What I want is to be able to write the entire OSX GUI in C++, instead of ObjC, and still use Cocoa. I doubt that is going to happen, and ObjectiveC is really a pain in the ass for us compared to C++, to the point where some programs we just don't bother to spend the extra time making OSX versions for.
Even if the chipset is locked down, simply using a little endian instead of big endian will make a world of difference with windows compatibility.
Now, if only they could support C++ with Cocoa, because I would rather go back and program in BASIC then use that horrible backwards of a language "Objective C".
Screw up your lilo config again?
When slipstreaming a SP into Windows 2000 or XP, I've just used "Bart's Boot Image Extractor" (bbie.exe) to extract the boot sectory from the original CD, and burned a bootable CD with Nero. It works just fine.