Your explanation for setting up ActiveSync means the account you have is connected by an incompetent IT department.
Setting up an Android or an iPhone for Exchange needs only an email address and a password. There are at least 3 different means by which Autodiscover can be configured to take care of client device configuration. If your IT dept can't figure that out, what makes you think a BES server is within their capacity to manage?
Your shrill denunciation of SSL and the assumption that users are too stupid to use a password seems almost self-denigrating. You don't use SSL in any web app? You can't remember your corporate credentials? The iPhone might be too complicated for you.....
Finally, we see the issue - you have a phone you don' t like, so it must be someone else's fault. The phone you did like was designed and built by a company so incompetent they self-destructed. It must be someone else's fault. I'm starting to see a pattern here....
>>> professors in the field of education tend to be some of the greatest contributors to the various scientific fields >>>
Can you please point to the big research universities that do NOT accept Federal funding? Where do you think all that grant money comes from?
Are you implying that there is no political bias in university research? Or just in the education departments of said universities?
Politics is an inherent component of human endeavor, we just aren't used to seeing such ham-fisted approaches as used by the incumbent Canadian government. The US Gov't has a lot more experience channeling research results into the harness of political imperatives WITHOUT getting caught doing same.
Facebook is foolish; I just got a small setup in from Rackable for a client of mine. Spendy, but very well done, it will be cheap to keep over the next 3 years. Great pre-sales support, great install support, complete power and heat profile up front, and 50% more $$$ up front than a generic Dell rack system. Considering the track record of Dell for this same client over the last 8 years, the client will be $$$ ahead in less than 18 months. We just downsized the cooling system for the server room (!!!!) and the double redundant 48V power system is the bomb. I don't dig the SGI rebranding, but the Rackable folks know their stuff.
It sounds as if Facebook feels entitled to loudly complain in order to get free/promo hardware. I guess Rackable wouldn't front them a couple of the ICE datacenter modules. Losing customers like Facebook sounds like a win.
Don't you have a modern mobility enabled workforce? The majority of users at my client sites use notebooks, and Windows XP/Vista with Offline Files is indispensable, along with Outlook in Cached Mode. Nice to think you can run everything off an NFS mount in a call center, but that ain't even remotely the end all be all (get it, remotely?).
Group Policies are one of the many great things about AD, regardless of what those ignorant of the real-life applications may say.
As for the huge number of apps that don't run correctly if you're not admin equivalent, welcome to 2009, things have changed quite a bit in the last 10 years. Would that you could say the same for Linux on the desktop.
Hmmmm, NDS on NW4 came out in *late* 1992, they had a deal where you bought NW3.11 and then you'd get NW4 for free. It didn't work at ALL, not in any meaningful way. Amazingly terrible. NW4.01 came out in late 93, it worked to a degree. Unfortunately, it had a limit of 2700 objects per container, which really screwed 3Com (they were migrating off their own NOS to NW4). NW4.02 came out in early 94 and it worked OK, since it was the accumulated patches needed to make the 3Com migration work. Unfortunately, it was still a LOT of work to migrate a NW3 shop to NDS.
NW4.1 came out in late 94 and finally separated the NDS database out of the kernel so you could upgrade one without upgrading the other. Unfortunately, it ATE a whole lot of 4.02 installs when it upgraded them. They patched their way around this with a different DSREPAIR, but basically Novell screwed any of their early adopters multiple times.
This meant that NT had plenty of time to get the kinks sorted out. Keep in mind that NT351 had a darn good NetWare migration utility (called VISINE because it got the red out) for NetWare 3.x shops. It also introduced File & Print Services for NetWare which was an emulator so NetWare client machines (DOS clients & Windows) could logon to NT *unchanged*. Microsoft took advantage of Novell's missteps, but Novell flat blew it.
I met a lot of interesting NetWare admins at a class M$ put on in sF back in late 94, we had a lot of fun with the presenter because he was far more conversant in NT than NetWare, but everyone came away wondering if Novell was going to make it. Very sad to see them go like this.
Yep, I still have a stash of those NIC's, they were the 2nd gen Intel PRO/100B (first gen was not great). I bought a value pack (5 NIC's plus a 12-port Bay Networks FE hub rebranded by Intel). Intel was loss leading to get a foothold in the market at the same time 3Com came out with the atrocious 3C590/595 and I quite buying 3Com (apparently so did everyone else). I was impressed and bought a bunch of new servers with that specific NIC. Used them for a bunch of customer sites as well.
Fabulous card, Intel promised the future drivers would optimize the firmware for Novell NetWare/Windows NT servers even though the shipping drivers wouldn't. I was transitioning from NetWare 3.x to NT351, and by Sept. 96 to NT4. The new drivers did improve performance in the servers, just as advertised.
They also wrote the drivers for FreeBSD (2.2.x can't remember, maybe 3?) and they were *really* fast for the day. FTP from a Windows server at like 6.5 MB/sec (P133's on both ends) was HUGE when compared to 10Base-T at 800 KB/sec.
The hack for ganging together the later PRO/100+ or PRO/100S desktop adapters was to stick one server adapter in and then you could use the onboard NIC's and any other PRO/100. The dual-port PRO/100+'s worked really well with Cisco's FEC on HP's switches, for example. Sweet.
When those kiosks went in to the local Post Office, they had a greeter who explained their function and features. It was explicity part of the "script" that the transaction was accompanied by a photograph for security purposes.
Seems to me someone needs some PayPal donations to subsidize their fight for your freedom so they announced this as an FOIA issue. Oh, what do you know, donations are the first item on their main page!
A Case for Redundant Arrays of Inexpensive Disks (RAID)
Since they fellows that invented it used the term first *15 years ago*, I think you might want to reconsider your ignorant stance and save the rubbish for the bin.
Nope, WD-40 is an electronics water dispersal formulation, happens to be a decent penetrating oil as well. It will leave a gummy residue on a surface that's not cleaned. If it penetrates to internal mechanisms not typically disassembled and cleaned (eg. firing pin channel and firing pin) it can gum up - or worse, cook & carbonize after a long shooting session.
This is also why it's a crummy lubricant; use BreakFree CLP if Hoppe's isn't enough for you.
Model railroaders know this as well - don't use WD-40 on your electric motors, you will be sad.
I dunno, but when I think admin/engineer, I think someone must know *something* about the target of their advocacy affections. Looking back 10 years ago, Novell killed off their domain services for NW3 to push people to NDS/NW4.
Funny thing is, many shops held on to NW3 (even with the "free" upgrade promo to NW4 until they needed a general-purpose operating system and then moved to NT3.5 (and Visine - "gets the red out").
Unfortunately, NetWare 4.0 didn't work AT ALL (if you'd ever installed it, let alone worked with it, you would know that). NetWare 4.01 *barely* worked, which 3Com found out when they tried to implement the marketing speak (oh, yeah, no more than 3700 objects within a container, sorry!). NetWare 4.02 was the direct outcome of the 3Com experience, and it sorta worked (still with monolithic NDS kernel). Shucks, they even gave all those pathetic customers free upgrades to 4.1!! Oh, sorry, 3 weeks after we shipped your upgrade, we released an ndsrepair you MUST run before you upgrade or you will destroy your 4.02 implementation.
Novell screwed their customer base again and again and again and again and again. Microsoft is not a "genius" company, they're just not brain-dead at this point. Novell just shows how long it takes for a moderately large company to die off in this marketspace.
AD 1.0 shipping in 2/2000 was so much better than NDS for 4-5 revisions that it's not even funny. Again, M$ will charge you for the privilige, but at least you get a kiss before you're bent over. Novell never figured that out.
If you don't know shit, you must post it on/. You must never have seen an MN.
1) They're contemporaneous to the Krag Jorgensen (.30-40 Krag) of Spanish American War fame, and similar in the smoothness of their actions, though the stripper clip loading of the MN is far superior in combat (as were the Mausers superior to the Krag's in that war, leading to the '03 Springfield/Mauser). 2) 7.62x54 Rimmed even looks like.30-40 (or.303 British) and has similar power, is widely available as surplus, new (cheap), and new (hunting grade). Czech ammo with 203 gr. soft point bullets is inexpensive ($6/box) and reasonably accurate. Surplus corrosive is *very* cheap, $2/box, while non-corrosive new mfg fmj in steel cases is $4 box.
Much more shootable than a Mauser since all the Warsaw Pact neo-NATO countries are making cheap new ammo (as is Tusla in RU). Of all the surplus rifles out there, this makes it by far the best deal - Lee-Enfields and Mausers are a lot more expensive to enjoy.
Tons of fun, excellent muzzle blast and recoil, not as much power as a.30-06 but a lot cheaper to shoot.
My recollection of the Slant-6's genesis was that it derived/inspired from/by a Porsche design for a tank/armored vehicle engine. The goal was to get a very long stroke but have a low block height (undersquare bore/stroke ratio). I recall the aluminum version - didn't they put out a Sprint pack early on? Friend of mine had (might still have) a 65-6 Valiant convertible with a 225(might have been 200?) and a Hurst 4-spd. Neat car, 300K plus on it's 4th top & first engine.
I'm writing this on an MSI KT3 Ultra ARU/xP2100 with 2 x 60 GB Maxtor stripe-set. I really like the FastTrak133 controller, and the whole system boots into XP in less than 30 seconds. This is the first system I've ever had that felt fast for more than two weeks (the autobahn effect). I'm still happy with it after 5 months, by far the all time record.
Since I'm not an illiterate moron, I store all my data on mirrored and duplexed volumes on a dual cpu / ecc ram / dual power supply / ups'd / DAT backed up fileserver.
Whining about a stupid user trick and somehow blaming it on your RAID controller is pretty funny. Since it's not redundant in a stripe set, what makes you think it has anything to do with RAID? Your controller was perfectly capable of creating a mirrored set, you know.
I was the human tape changer 12 years ago on a SUN 490 with one of the very first RAID5 arrays. The purpose of RAID3/4/5 was to get the biggest volumes from the cheapest (most inexpensive) drives without sacrificing data integrity. It was never for performance reasons, and it still needed backup.
This is an updated client that has a much improved user interface (session bar at the top, annoying reminder you haven't logged off) and the ability to redirect USB printers (or old serial printers, I haven't one to try). The correctly named drivers must exist on the host server, but they map fine. This is a big deal for telecommuting as most/many consumer oriented printers are USB only at this point.
For.NET, the local drives of the client (including mapped network drives) map over to the server session (probably works with WinXP Pro as well, haven't fiddled with that aspect).
Other USB/serial devices (e.g. old DB-9 hotsync cradles) may or may not work depending on client and server version. Wouldn't cross my fingers on anything other than printers.
Uh, sorry, read RFC 1812 for requirements for Internet routers (circa 7/95 mabye??).
RIPv2 has more sophisticated support for route aggregation that CIDR allows for, but RIPv1 works fine (given that it's RIP, of course).
M$ OS's have worked properly with the 0 subnet for a LONG time, since at least mid-95, by the way, and this was BEFORE Cisco properly implemented 1812 (everyone seems stuck on 950).
Slashdot Mirror
Your explanation for setting up ActiveSync means the account you have is connected by an incompetent IT department.
Setting up an Android or an iPhone for Exchange needs only an email address and a password. There are at least 3 different means by which Autodiscover can be configured to take care of client device configuration. If your IT dept can't figure that out, what makes you think a BES server is within their capacity to manage?
Your shrill denunciation of SSL and the assumption that users are too stupid to use a password seems almost self-denigrating. You don't use SSL in any web app? You can't remember your corporate credentials? The iPhone might be too complicated for you.....
Finally, we see the issue - you have a phone you don' t like, so it must be someone else's fault. The phone you did like was designed and built by a company so incompetent they self-destructed. It must be someone else's fault. I'm starting to see a pattern here....
Regards,
Brian in CA
>>>
professors in the field of education tend to be some of the greatest contributors to the various scientific fields
>>>
Can you please point to the big research universities that do NOT accept Federal funding? Where do you think all that grant money comes from?
Are you implying that there is no political bias in university research? Or just in the education departments of said universities?
Politics is an inherent component of human endeavor, we just aren't used to seeing such ham-fisted approaches as used by the incumbent Canadian government. The US Gov't has a lot more experience channeling research results into the harness of political imperatives WITHOUT getting caught doing same.
Regards,
Brian in CA
Uhh, ever hear of the EISA partition? Probably not.
Regards,
Brian in CA
Facebook is foolish; I just got a small setup in from Rackable for a client of mine. Spendy, but very well done, it will be cheap to keep over the next 3 years. Great pre-sales support, great install support, complete power and heat profile up front, and 50% more $$$ up front than a generic Dell rack system. Considering the track record of Dell for this same client over the last 8 years, the client will be $$$ ahead in less than 18 months. We just downsized the cooling system for the server room (!!!!) and the double redundant 48V power system is the bomb. I don't dig the SGI rebranding, but the Rackable folks know their stuff.
It sounds as if Facebook feels entitled to loudly complain in order to get free/promo hardware. I guess Rackable wouldn't front them a couple of the ICE datacenter modules. Losing customers like Facebook sounds like a win.
Regards,
Brian in CA
Don't you have a modern mobility enabled workforce? The majority of users at my client sites use notebooks, and Windows XP/Vista with Offline Files is indispensable, along with Outlook in Cached Mode. Nice to think you can run everything off an NFS mount in a call center, but that ain't even remotely the end all be all (get it, remotely?).
Group Policies are one of the many great things about AD, regardless of what those ignorant of the real-life applications may say.
As for the huge number of apps that don't run correctly if you're not admin equivalent, welcome to 2009, things have changed quite a bit in the last 10 years. Would that you could say the same for Linux on the desktop.
Regards,
Brian in CA
Not dual core, dual processor (4 cores). Or 16 cores in the case of the 4-way 8300's.
Regards,
Brian in CA
They'll listen to Reason.
Only great book he's written so far.
Hmmmm, NDS on NW4 came out in *late* 1992, they had a deal where you bought NW3.11 and then you'd get NW4 for free. It didn't work at ALL, not in any meaningful way. Amazingly terrible. NW4.01 came out in late 93, it worked to a degree. Unfortunately, it had a limit of 2700 objects per container, which really screwed 3Com (they were migrating off their own NOS to NW4). NW4.02 came out in early 94 and it worked OK, since it was the accumulated patches needed to make the 3Com migration work. Unfortunately, it was still a LOT of work to migrate a NW3 shop to NDS.
NW4.1 came out in late 94 and finally separated the NDS database out of the kernel so you could upgrade one without upgrading the other. Unfortunately, it ATE a whole lot of 4.02 installs when it upgraded them. They patched their way around this with a different DSREPAIR, but basically Novell screwed any of their early adopters multiple times.
This meant that NT had plenty of time to get the kinks sorted out. Keep in mind that NT351 had a darn good NetWare migration utility (called VISINE because it got the red out) for NetWare 3.x shops. It also introduced File & Print Services for NetWare which was an emulator so NetWare client machines (DOS clients & Windows) could logon to NT *unchanged*. Microsoft took advantage of Novell's missteps, but Novell flat blew it.
I met a lot of interesting NetWare admins at a class M$ put on in sF back in late 94, we had a lot of fun with the presenter because he was far more conversant in NT than NetWare, but everyone came away wondering if Novell was going to make it. Very sad to see them go like this.
Regards,
Brian in CA
Fabulous card, Intel promised the future drivers would optimize the firmware for Novell NetWare/Windows NT servers even though the shipping drivers wouldn't. I was transitioning from NetWare 3.x to NT351, and by Sept. 96 to NT4. The new drivers did improve performance in the servers, just as advertised.
They also wrote the drivers for FreeBSD (2.2.x can't remember, maybe 3?) and they were *really* fast for the day. FTP from a Windows server at like 6.5 MB/sec (P133's on both ends) was HUGE when compared to 10Base-T at 800 KB/sec.
The hack for ganging together the later PRO/100+ or PRO/100S desktop adapters was to stick one server adapter in and then you could use the onboard NIC's and any other PRO/100. The dual-port PRO/100+'s worked really well with Cisco's FEC on HP's switches, for example. Sweet.
Thanks for reminding me of the olden days.
When those kiosks went in to the local Post Office, they had a greeter who explained their function and features. It was explicity part of the "script" that the transaction was accompanied by a photograph for security purposes.
Seems to me someone needs some PayPal donations to subsidize their fight for your freedom so they announced this as an FOIA issue. Oh, what do you know, donations are the first item on their main page!
Rubbish?
- 39 1
http://sunsite.berkeley.edu/TechRepPages/CSD-87
A Case for Redundant Arrays of Inexpensive Disks (RAID)
Since they fellows that invented it used the term first *15 years ago*, I think you might want to reconsider your ignorant stance and save the rubbish for the bin.
Nope, WD-40 is an electronics water dispersal formulation, happens to be a decent penetrating oil as well. It will leave a gummy residue on a surface that's not cleaned. If it penetrates to internal mechanisms not typically disassembled and cleaned (eg. firing pin channel and firing pin) it can gum up - or worse, cook & carbonize after a long shooting session.
This is also why it's a crummy lubricant; use BreakFree CLP if Hoppe's isn't enough for you.
Model railroaders know this as well - don't use WD-40 on your electric motors, you will be sad.
Regards,
Brian in CA
I dunno, but when I think admin/engineer, I think someone must know *something* about the target of their advocacy affections. Looking back 10 years ago, Novell killed off their domain services for NW3 to push people to NDS/NW4.
Funny thing is, many shops held on to NW3 (even with the "free" upgrade promo to NW4 until they needed a general-purpose operating system and then moved to NT3.5 (and Visine - "gets the red out").
Unfortunately, NetWare 4.0 didn't work AT ALL (if you'd ever installed it, let alone worked with it, you would know that). NetWare 4.01 *barely* worked, which 3Com found out when they tried to implement the marketing speak (oh, yeah, no more than 3700 objects within a container, sorry!). NetWare 4.02 was the direct outcome of the 3Com experience, and it sorta worked (still with monolithic NDS kernel). Shucks, they even gave all those pathetic customers free upgrades to 4.1!! Oh, sorry, 3 weeks after we shipped your upgrade, we released an ndsrepair you MUST run before you upgrade or you will destroy your 4.02 implementation.
Novell screwed their customer base again and again and again and again and again. Microsoft is not a "genius" company, they're just not brain-dead at this point. Novell just shows how long it takes for a moderately large company to
die off in this marketspace.
AD 1.0 shipping in 2/2000 was so much better than NDS for 4-5 revisions that it's not even funny. Again, M$ will charge you for the privilige, but at least you get a kiss before you're bent over. Novell never figured that out.
Regards,
Brian in CA
If you don't know shit, you must post it on /. You must never have seen an MN.
.30-40 (or .303 British) and has similar power, is widely available as surplus, new (cheap), and new (hunting grade). Czech ammo with 203 gr. soft point bullets is inexpensive ($6/box) and reasonably accurate. Surplus corrosive is *very* cheap, $2/box, while non-corrosive new mfg fmj in steel cases is $4 box.
.30-06 but a lot cheaper to shoot.
1) They're contemporaneous to the Krag Jorgensen (.30-40 Krag) of Spanish American War fame, and similar in the smoothness of their actions, though the stripper clip loading of the MN is far superior in combat (as were the Mausers superior to the Krag's in that war, leading to the '03 Springfield/Mauser).
2) 7.62x54 Rimmed even looks like
Much more shootable than a Mauser since all the Warsaw Pact neo-NATO countries are making cheap new ammo (as is Tusla in RU). Of all the surplus rifles out there, this makes it by far the best deal - Lee-Enfields and Mausers are a lot more expensive to enjoy.
Tons of fun, excellent muzzle blast and recoil, not as much power as a
My recollection of the Slant-6's genesis was that it derived/inspired from/by a Porsche design for a tank/armored vehicle engine. The goal was to get a very long stroke but have a low block height (undersquare bore/stroke ratio). I recall the aluminum version - didn't they put out a Sprint pack early on? Friend of mine had (might still have) a 65-6 Valiant convertible with a 225(might have been 200?) and a Hurst 4-spd. Neat car, 300K plus on it's 4th top & first engine.
I'm writing this on an MSI KT3 Ultra ARU/xP2100 with 2 x 60 GB Maxtor stripe-set. I really like the FastTrak133 controller, and the whole system boots into XP in less than 30 seconds. This is the first system I've ever had that felt fast for more than two weeks (the autobahn effect). I'm still happy with it after 5 months, by far the all time record.
Since I'm not an illiterate moron, I store all my data on mirrored and duplexed volumes on a dual cpu / ecc ram / dual power supply / ups'd / DAT backed up fileserver.
Whining about a stupid user trick and somehow blaming it on your RAID controller is pretty funny. Since it's not redundant in a stripe set, what makes you think it has anything to do with RAID? Your controller was perfectly capable of creating a mirrored set, you know.
I was the human tape changer 12 years ago on a SUN 490 with one of the very first RAID5 arrays. The purpose of RAID3/4/5 was to get the biggest volumes from the cheapest (most inexpensive) drives without sacrificing data integrity. It was never for performance reasons, and it still needed backup.
Sheesh.
This is an updated client that has a much improved user interface (session bar at the top, annoying reminder you haven't logged off) and the ability to redirect USB printers (or old serial printers, I haven't one to try). The correctly named drivers must exist on the host server, but they map fine. This is a big deal for telecommuting as most/many consumer oriented printers are USB only at this point.
.NET, the local drives of the client (including mapped network drives) map over to the server session (probably works with WinXP Pro as well, haven't fiddled with that aspect).
For
Other USB/serial devices (e.g. old DB-9 hotsync cradles) may or may not work depending on client and server version. Wouldn't cross my fingers on anything other than printers.
Regards,
Brian in CA
Uh, sorry, read RFC 1812 for requirements for Internet routers (circa 7/95 mabye??).
RIPv2 has more sophisticated support for route aggregation that CIDR allows for, but RIPv1 works fine (given that it's RIP, of course).
M$ OS's have worked properly with the 0 subnet for a LONG time, since at least mid-95, by the way, and this was BEFORE Cisco properly implemented 1812 (everyone seems stuck on 950).
Regards,
Brian in CA