> Blah. I'm running Linux with ext4 on my Samsung SSD 840 EVO 250GB (EXT0BB6Q). > Am I totally screwed?
Not totally as long as your chipset is supported, but almost.
All you need to do is extract actual SSD firmware upgrade file from Windows executable, then create freedos bootable USB stick, copy DOS updater files extracted from older Samsung DOS updater download and add those new SSD firmware from new Windows updater to your custom upgrade USB stick. After you have managed to upgrade SSD firmware boot system using some live linux and do non-destructive badblocks read+rewrite scan over entire SSD.
In my opinion this is only good solution proposed so far. With Instant one gets most benefits of controller based solution without actually purchasing controller.
Ziggo tunnels visitor traffic so customer that hosts access point don't need to worry about cops knocking on door due someone else abusing connection. It's same way Finnish provider "Wippies" did years ago before closing down. This is also right way to solve this problem and also fixes at least routing and session persistence issues with roaming between access points. Other roaming issues such as client sticking to distant AP may still be present if there's no AP-to-AP RF management features like those in Aruba, Cisco etc. enterprise wireless (controller based) solutions.
Don't forget Hauppauge i486 motherboard that had i860 on it. Not quite i960, but still RISC. Pretty much only thing you could do with i860 side was running sample application included on floppies that rotated some characters on upper right corner of screen - and that rotation persisted over reboot with ctrl+alt+delete. Whoo, multi-processing! I think i860 processor on that motherboard was intended to be used together with bundled non-standard display adapter for some sort of CAD use.
I actually had one of those, got it from some bankrupt company with full manuals, compiler for i860 etc. Shame I've lost it over years as I doubt there's many of those left today. Even had that custom display adapter and bunch of technical information from factory as it was some sort of pre-production sample sent to company importing Hauppauge products.
Storing PST files on Windows fileserver is bad idea just like that KB article says. I've seen it and it's actually more evil than just being slow. It causes drive mappings to stall for anything from few seconds to over minute. Since Windows clients always search dlls, exes etc. first from your homeshare all workstations stop working for same period of time. There's nothing on logs, no error messages, no suspicious perfmon values, no errors visible with network sniffer. PC's and server will just pause for that 1 second to 1+ minute. That's with dualcore CPU, several gigabytes of ram, hardware RAID 1+0, dual gigabit network etc. with only ~50 users. You'll also start seeing filesystem corruption. Not files itself, but ownership and permissions get mangled. There's hotfix MS is trying to hide that fixes this corruption... Well anyway it's fixed on Win2003 SP2 so they don't need to admit it anymore just suggest installing SP2.
Couple years ago HP sent me replacement disk for NC6000 laptop after old one died. Disk they sent was in sealed package and looked like new. However when I installed it to laptop and turned power on there was some odd boot-loader present. Little more investigating with recovery tool revealed previous owners files among diagnostics report showing serial number of computer disk was previously used. There weren't much files on disk, but enough to reveal name of company in Asia that had sent it back to HP for warranty work. Disk itself was just fine so it looks like HP ran some tests and repackaged it after passing tests but didn't wipe old files. Previous owner probably just had corrupt OS install or some other hardware problem incorrectly diagnosed as harddisk fault.
I complained to HP and included all serials and information about previous owner so they could check what went wrong with their warranty process. They weren't interested and just said they're very sorry and disks are usually wiped. Further they also said there's no way for them to track history of spares sent nor check computer warranty history based on serialnumber. It's pretty clear that they can do both, but just don't care. Great, so when I send broken disk that I can't wipe myself back to HP they might fix it and forgot to wipe and it's no problem.
D-Link DFL-700 router runs WinXP quite well. It has 266 MHz AMD Geode (486 class CPU) and 64MB RAM. Just connect keyboard and VGA to debug connectors onboard (get pinout from Lanier website - they're actual board manufacturer) and plugin laptop HDD instead of non-standard flash-drive they ship with.
Almost 10 years ago there was pretty much what you want for VB5. I still have original announce email and even necessary binaries to try it for DOS, SCO, Linux, AIX etc. I can post binaries with readme and sample code if someone is interested. Let me know.
Sounds like MSI K7D with onboard Intel Pro/100. This seems to be common problem as regular Intel Pro/100 don't support that chip. Drivers that come with Windows doesn't have support for it either. What you need is Windows XP Embedded drivers for i8255x from Intel's website.
Actually 3,5" 15krpm drives have very small platters inside, not much bigger than those used in regular 2,5" drives. I don't know if 2,5" 15000 rpm drives have even smaller ones.
No it doesn't - unless ProGrabber was present on disk before you installed Windows. Since you likely installed it from Windows it's called Progra~2 instead. Short filenames are created at the same time with long ones and they don't change when something overlapping is created, new one just gets mangled slightly differently.
Actually there's embedded x86 processors on market. Not from Intel but RDC. There's some conflicting information on web, but RDC R3211 is actually x86 and for example Linksys WRT54GR uses it and runs x86 Linux.
There's also NS/AMD Geode. Of course not everyone agrees which use should be categorized as embedded. Probably neither Geode nor RDC is used on cell phones.
Couple years ago my previous TV exploded while I was watching some movie from TV. First I thought that whoa this movie has awesome effects and sounds. Pretty soon I realized that sparks and awful smelling mushroom cloud emerging from behind TV-set was not part of movie.:) Luckily it only sparked and smoked but didn't catch fire.
Err not exactly. That was true for Win2000 Pro and Server since they shared common NT kernel. Of course MS said they're different like they used to do with NT 3.x and 4. WinXP and Win2003 do have different internals so this time MS is telling truth.
Couple months ago we still had old Quad Xeon Exchange 5.5 server (Proliant 6000 from 1999) running. CPU 2 of 4 failed, server restarted itself, disabled faulty CPU and generated alert via management software. WinNT4 EE and Exchange it was running worked just fine with 3 processors instead of 4 that used to be there for last 6 years.
Back when Pentium Pro was considered highend ALR created 6 CPU server that used two 3 CPU processor cards. You could use 3 or 6 processors on that server as well so no need to go with usual steps 1/2/4/8. Don't know if 5 CPUs was valid configuration.
Couple years ago when 10G and 20G Fujitsu HDD's started failing on our workstations (pre-merger Compaqs) I ran script to scan units with Fujitsu ones since some of them had WD, Seagate etc. Next I sent serials of units with Fujitsu disks to Compaq and wrote that as you know all of these have faulty HDD, please sent technician with spares ASAP. Took 30 minutes and my phone ringed. Someone dork from Compaq called and said that since those HDDs are still working they wont replace them. Also denied that there's any problem with Fujitsu HDDs and claimed that 20 or so dead Fujitsu disks they replaced for us within month was normal. This guy personally handled at least half of them and still had nerve to deny that failure rate was way above normal. Anyway I told him that if necessary each and every one of those disks will be totally broken by time their repair guys arrive since I have this big and heavy hammer. Next this tech support monkey said they won't replace any disk for us ever since we break them ourself with hammer and it voids warranty. Asked for his supervisor who was no better. Following day I managed to reach someone smarter with phone and eventually they did replace all Fujitsus with another brand while disks were still functional. Six months later they even admitted this problem publicly on web.
So if you're big customer and own lot of these potentially faulty devices call to manufacturer and demand that they proactively replace all suspect devices. Don't settle less. Even this will cause extra expenses to you but it's lot less than flaky hardware crashing on users will cause. You can also make schedule for replacements so impact for users productively is minimal.
We have all workstations configured with local firewall rules that prohibit most outbound traffic unless IP address is from our intranet address range. If it's not only DHCP client, DNS client, AV updates and VPN to corporate network is allowed. Inbound traffic is completely blocked when plugged to foreign network. Even when within our network there's strict rules blocking everything as default and only allowing limited set of ports if traffic is coming from subnet used by helpdesk.
Visitors used to plug their laptops to our internal net, but we implemented 802.1x and it's no longer problem. Locations that couldn't be updated to it due various reasons are routed to separate firewall interface (VLAN) and can access corporate net (and internet) only thru VPN.
Printers and other devices that don't speak 802.1x are on separate VLANs that have no access to corporate net or internet.
This is all very basic stuff that any decent admin should be able to implement easily. Everything can be done in typical Active Directory + Win2000/XP/2003 environment without third-party software. Therefore implementing infrastucture like this is even cheap.
Since someone is going to ask how to limit outbound traffic with Win2k/XP built-in firewall here's answer: Use either RAS filtering (per machine VBS) or IPSEC group-policies.
Because all internet traffic is forced thru proxies doing antivirus checks at HQ those blocking rules aren't problem. Users simply access net using our main connection and their own is only used to tunnel everything via VPN. Users don't have local admin rights so they can't disable firewall to bypass security.
Biggest drawback with this kind of implementation is WLAN access. Since many WLANs require login using web browser and net access is denied unless VPN is active they're unusable. There's no easy solution to this. Only good solution would be some very restricted and secure browser that's allowed to access 80/443 ports. Preferrably running in own virtualmachine/sandbox to protect computer itself.
Original IDE (called ATID back then) 16-bit controllers were just couple simple IC's connecting IDE ribbon-cable to ISA bus. When VLB and PCI came there was need for separate controller chips (for example RZ1000 and CMD640) so original idea of having all controller logic on HDD was no longer true.
XTID was different thing. Controllers had several chips, on-board BIOS etc. They also required XTID versions of HDDs so you couldn't use ATID version. There was some rare disks that had jumper to choose between XTID and ATID modes. I think it was one specific 40MB Seagate model 3.5" LP aka Slim-Line.
Only manufacturer I know that made pure XTID drives was Western Digital. Installed couple of those with 8-bit XTID controller in mid 90's. They were antique even back then. I don't know where those WD XTID HDD's came to market here in Finland. Finding XTID controller (for x86 machine) was even harder. I think I had those two XTID disks in shelf for years until I found XTID controller in some surplus stores junk pile.
Back when Plus Hard Card was new thing there were no such thing as IRQ 14 or 15 on typical PC. IBM PC was still running on 4,77MHz and using 8-bit slots with IRQ's 2-7. It was not even possible to install it to 16-bit slot of IBM AT because 16-bit part of ISA slot was blocked by frame of card. Of course most AT systems had also 8-bit slots for this particular reason so installation was still possible.
They didn't use IDE-like drives either. Controller part of board was fairly complex with multiple large chips.
There were lot of clones that were'nt as plug-and-play as original Plus Hard Card was. Clones were just 8-bit MFM/RLL (and later 16-bit MFM/RLL/IDE/ESDI/SCSI) controllers mounted to metal plate with normal 3,5" HDD.
Quantum bought Hard Card manufacturer eventually as someone already wrote.
Hard Cards from various manufacturers lasted quite long. I'd say around 10 years eg. from 1985 to mid 90's. I considered 10 years pretty long time in computer industry.
>> Intel had the 586-driven smart-cards, and I believe 3Com had them as well. >You're probably thinking of the i960-based cards
Actually Intel did have "586" named chip well before 486. Most people assume 586 means first Pentium processor, but they already used that number in late 80's. Never seen Intel ethernet card with one, but 3Com 3C505 aka Etherlink+ used it. 586 chip was ceramic version that got burning hot. 3C505 was supposed to be somekind of smart ethernet card and to be used with 3Com's own network OS. It never succeeded. There were drivers for Netware as well and that's what we used.
What you think would happen if everyone disabled upload and be leech like you? Exactly, there would be no more Kazaa of any other P2P network left. Therefore I'm confident that Inburito is actually RIAA/MPAA employee. Beware!
Actually Hydra was released as Windows NT 4.0 Terminal Server Edition. Later same technology was included in Windows 2000 Server, 2003 Server and WinXP workstation (RDP, Remote Desktop, Fast User Switching).
I remember seeing Windows NT 3.5 (not 3.51) based "Citrix Winframe for Networks" in production around late 1995. WinNT4 TSE (=Hydra) came three years later.
Of course Hydra was just forked Citix Winframe without support for ICA..
Slashdot Mirror
http://stevetodd.typepad.com/m...
Read that post written by Steve. It explains reasons why DG decided to use Windows NT for Clariion.
> Blah. I'm running Linux with ext4 on my Samsung SSD 840 EVO 250GB (EXT0BB6Q).
> Am I totally screwed?
Not totally as long as your chipset is supported, but almost.
All you need to do is extract actual SSD firmware upgrade file from Windows executable, then create freedos bootable USB stick, copy DOS updater files extracted from older Samsung DOS updater download and add those new SSD firmware from new Windows updater to your custom upgrade USB stick. After you have managed to upgrade SSD firmware boot system using some live linux and do non-destructive badblocks read+rewrite scan over entire SSD.
In my opinion this is only good solution proposed so far. With Instant one gets most benefits of controller based solution without actually purchasing controller.
I assume provider you described is Ziggo? There's technical description of their solution on http://www.technischweekblad.nl/hotspot-groningen.297341.lynkx. Google translate turns it to good enough English.
Ziggo tunnels visitor traffic so customer that hosts access point don't need to worry about cops knocking on door due someone else abusing connection. It's same way Finnish provider "Wippies" did years ago before closing down. This is also right way to solve this problem and also fixes at least routing and session persistence issues with roaming between access points. Other roaming issues such as client sticking to distant AP may still be present if there's no AP-to-AP RF management features like those in Aruba, Cisco etc. enterprise wireless (controller based) solutions.
Don't forget Hauppauge i486 motherboard that had i860 on it. Not quite i960, but still RISC. Pretty much only thing you could do with i860 side was running sample application included on floppies that rotated some characters on upper right corner of screen - and that rotation persisted over reboot with ctrl+alt+delete. Whoo, multi-processing! I think i860 processor on that motherboard was intended to be used together with bundled non-standard display adapter for some sort of CAD use.
I actually had one of those, got it from some bankrupt company with full manuals, compiler for i860 etc. Shame I've lost it over years as I doubt there's many of those left today. Even had that custom display adapter and bunch of technical information from factory as it was some sort of pre-production sample sent to company importing Hauppauge products.
http://www.geekdot.com/index.php?page=hauppauge-4860
Storing PST files on Windows fileserver is bad idea just like that KB article says. I've seen it and it's actually more evil than just being slow. It causes drive mappings to stall for anything from few seconds to over minute. Since Windows clients always search dlls, exes etc. first from your homeshare all workstations stop working for same period of time. There's nothing on logs, no error messages, no suspicious perfmon values, no errors visible with network sniffer. PC's and server will just pause for that 1 second to 1+ minute. That's with dualcore CPU, several gigabytes of ram, hardware RAID 1+0, dual gigabit network etc. with only ~50 users. You'll also start seeing filesystem corruption. Not files itself, but ownership and permissions get mangled. There's hotfix MS is trying to hide that fixes this corruption... Well anyway it's fixed on Win2003 SP2 so they don't need to admit it anymore just suggest installing SP2.
Couple years ago HP sent me replacement disk for NC6000 laptop after old one died. Disk they sent was in sealed package and looked like new. However when I installed it to laptop and turned power on there was some odd boot-loader present. Little more investigating with recovery tool revealed previous owners files among diagnostics report showing serial number of computer disk was previously used. There weren't much files on disk, but enough to reveal name of company in Asia that had sent it back to HP for warranty work. Disk itself was just fine so it looks like HP ran some tests and repackaged it after passing tests but didn't wipe old files. Previous owner probably just had corrupt OS install or some other hardware problem incorrectly diagnosed as harddisk fault.
I complained to HP and included all serials and information about previous owner so they could check what went wrong with their warranty process. They weren't interested and just said they're very sorry and disks are usually wiped. Further they also said there's no way for them to track history of spares sent nor check computer warranty history based on serialnumber. It's pretty clear that they can do both, but just don't care. Great, so when I send broken disk that I can't wipe myself back to HP they might fix it and forgot to wipe and it's no problem.
D-Link DFL-700 router runs WinXP quite well. It has 266 MHz AMD Geode (486 class CPU) and 64MB RAM. Just connect keyboard and VGA to debug connectors onboard (get pinout from Lanier website - they're actual board manufacturer) and plugin laptop HDD instead of non-standard flash-drive they ship with.
Almost 10 years ago there was pretty much what you want for VB5. I still have original announce email and even necessary binaries to try it for DOS, SCO, Linux, AIX etc. I can post binaries with readme and sample code if someone is interested. Let me know.
l opment.system/msg/3a0293334be4ec01
k sltd.com/vbvm.htmlc om/
http://groups.google.com/group/comp.os.linux.deve
http://web.archive.org/web/20010203155600/softwor
http://web.archive.org/web/*/http://softworksltd.
Sounds like MSI K7D with onboard Intel Pro/100. This seems to be common problem as regular Intel Pro/100 don't support that chip. Drivers that come with Windows doesn't have support for it either. What you need is Windows XP Embedded drivers for i8255x from Intel's website.
Actually 3,5" 15krpm drives have very small platters inside, not much bigger than those used in regular 2,5" drives. I don't know if 2,5" 15000 rpm drives have even smaller ones.
_ user_tip/15,000RPM%20HDD%20Cheetah%2015k.3.jpg
Here's first hit from google image search that shows how small they are. http://www.starthomepage.com/shp_upload/board/win
One of our users wrote passwords to monitor using permanent marker. That way they newer got lost when he changed location.
You can do that with Process Lasso. http://www.bitsum.com/ProSuper.asp
No it doesn't - unless ProGrabber was present on disk before you installed Windows. Since you likely installed it from Windows it's called Progra~2 instead. Short filenames are created at the same time with long ones and they don't change when something overlapping is created, new one just gets mangled slightly differently.
Actually there's embedded x86 processors on market. Not from Intel but RDC. There's some conflicting information on web, but RDC R3211 is actually x86 and for example Linksys WRT54GR uses it and runs x86 Linux.
There's also NS/AMD Geode. Of course not everyone agrees which use should be categorized as embedded. Probably neither Geode nor RDC is used on cell phones.
Couple years ago my previous TV exploded while I was watching some movie from TV. First I thought that whoa this movie has awesome effects and sounds. Pretty soon I realized that sparks and awful smelling mushroom cloud emerging from behind TV-set was not part of movie. :) Luckily it only sparked and smoked but didn't catch fire.
Err not exactly. That was true for Win2000 Pro and Server since they shared common NT kernel. Of course MS said they're different like they used to do with NT 3.x and 4. WinXP and Win2003 do have different internals so this time MS is telling truth.
Couple months ago we still had old Quad Xeon Exchange 5.5 server (Proliant 6000 from 1999) running. CPU 2 of 4 failed, server restarted itself, disabled faulty CPU and generated alert via management software. WinNT4 EE and Exchange it was running worked just fine with 3 processors instead of 4 that used to be there for last 6 years.
Back when Pentium Pro was considered highend ALR created 6 CPU server that used two 3 CPU processor cards. You could use 3 or 6 processors on that server as well so no need to go with usual steps 1/2/4/8. Don't know if 5 CPUs was valid configuration.
Here's screenshot from 3 CPU Xeon task damager: http://romikselle.com/Xeon.gif
Couple years ago when 10G and 20G Fujitsu HDD's started failing on our workstations (pre-merger Compaqs) I ran script to scan units with Fujitsu ones since some of them had WD, Seagate etc. Next I sent serials of units with Fujitsu disks to Compaq and wrote that as you know all of these have faulty HDD, please sent technician with spares ASAP. Took 30 minutes and my phone ringed. Someone dork from Compaq called and said that since those HDDs are still working they wont replace them. Also denied that there's any problem with Fujitsu HDDs and claimed that 20 or so dead Fujitsu disks they replaced for us within month was normal. This guy personally handled at least half of them and still had nerve to deny that failure rate was way above normal. Anyway I told him that if necessary each and every one of those disks will be totally broken by time their repair guys arrive since I have this big and heavy hammer. Next this tech support monkey said they won't replace any disk for us ever since we break them ourself with hammer and it voids warranty. Asked for his supervisor who was no better. Following day I managed to reach someone smarter with phone and eventually they did replace all Fujitsus with another brand while disks were still functional. Six months later they even admitted this problem publicly on web.
So if you're big customer and own lot of these potentially faulty devices call to manufacturer and demand that they proactively replace all suspect devices. Don't settle less. Even this will cause extra expenses to you but it's lot less than flaky hardware crashing on users will cause. You can also make schedule for replacements so impact for users productively is minimal.
We have all workstations configured with local firewall rules that prohibit most outbound traffic unless IP address is from our intranet address range. If it's not only DHCP client, DNS client, AV updates and VPN to corporate network is allowed. Inbound traffic is completely blocked when plugged to foreign network. Even when within our network there's strict rules blocking everything as default and only allowing limited set of ports if traffic is coming from subnet used by helpdesk.
Visitors used to plug their laptops to our internal net, but we implemented 802.1x and it's no longer problem. Locations that couldn't be updated to it due various reasons are routed to separate firewall interface (VLAN) and can access corporate net (and internet) only thru VPN.
Printers and other devices that don't speak 802.1x are on separate VLANs that have no access to corporate net or internet.
This is all very basic stuff that any decent admin should be able to implement easily. Everything can be done in typical Active Directory + Win2000/XP/2003 environment without third-party software. Therefore implementing infrastucture like this is even cheap.
Since someone is going to ask how to limit outbound traffic with Win2k/XP built-in firewall here's answer: Use either RAS filtering (per machine VBS) or IPSEC group-policies.
Because all internet traffic is forced thru proxies doing antivirus checks at HQ those blocking rules aren't problem. Users simply access net using our main connection and their own is only used to tunnel everything via VPN. Users don't have local admin rights so they can't disable firewall to bypass security.
Biggest drawback with this kind of implementation is WLAN access. Since many WLANs require login using web browser and net access is denied unless VPN is active they're unusable. There's no easy solution to this. Only good solution would be some very restricted and secure browser that's allowed to access 80/443 ports. Preferrably running in own virtualmachine/sandbox to protect computer itself.
Original IDE (called ATID back then) 16-bit controllers were just couple simple IC's connecting IDE ribbon-cable to ISA bus. When VLB and PCI came there was need for separate controller chips (for example RZ1000 and CMD640) so original idea of having all controller logic on HDD was no longer true.
XTID was different thing. Controllers had several chips, on-board BIOS etc. They also required XTID versions of HDDs so you couldn't use ATID version. There was some rare disks that had jumper to choose between XTID and ATID modes. I think it was one specific 40MB Seagate model 3.5" LP aka Slim-Line.
Only manufacturer I know that made pure XTID drives was Western Digital. Installed couple of those with 8-bit XTID controller in mid 90's. They were antique even back then. I don't know where those WD XTID HDD's came to market here in Finland. Finding XTID controller (for x86 machine) was even harder. I think I had those two XTID disks in shelf for years until I found XTID controller in some surplus stores junk pile.
Back when Plus Hard Card was new thing there were no such thing as IRQ 14 or 15 on typical PC. IBM PC was still running on 4,77MHz and using 8-bit slots with IRQ's 2-7. It was not even possible to install it to 16-bit slot of IBM AT because 16-bit part of ISA slot was blocked by frame of card. Of course most AT systems had also 8-bit slots for this particular reason so installation was still possible.
They didn't use IDE-like drives either. Controller part of board was fairly complex with multiple large chips.
There were lot of clones that were'nt as plug-and-play as original Plus Hard Card was. Clones were just 8-bit MFM/RLL (and later 16-bit MFM/RLL/IDE/ESDI/SCSI) controllers mounted to metal plate with normal 3,5" HDD.
Quantum bought Hard Card manufacturer eventually as someone already wrote.
Hard Cards from various manufacturers lasted quite long. I'd say around 10 years eg. from 1985 to mid 90's. I considered 10 years pretty long time in computer industry.
There's link to photo of original card. Text talks about smallest being 20 MB, but first model was actually 10 MB.
http://incolor.inebraska.com/bill_r/hardcard.htm
>> Intel had the 586-driven smart-cards, and I believe 3Com had them as well.
>You're probably thinking of the i960-based cards
Actually Intel did have "586" named chip well before 486. Most people assume 586 means first Pentium processor, but they already used that number in late 80's. Never seen Intel ethernet card with one, but 3Com 3C505 aka Etherlink+ used it. 586 chip was ceramic version that got burning hot. 3C505 was supposed to be somekind of smart ethernet card and to be used with 3Com's own network OS. It never succeeded. There were drivers for Netware as well and that's what we used.
What you think would happen if everyone disabled upload and be leech like you? Exactly, there would be no more Kazaa of any other P2P network left. Therefore I'm confident that Inburito is actually RIAA/MPAA employee. Beware!
Actually Hydra was released as Windows NT 4.0 Terminal Server Edition. Later same technology was included in Windows 2000 Server, 2003 Server and WinXP workstation (RDP, Remote Desktop, Fast User Switching).
I remember seeing Windows NT 3.5 (not 3.51) based "Citrix Winframe for Networks" in production around late 1995. WinNT4 TSE (=Hydra) came three years later.
Of course Hydra was just forked Citix Winframe without support for ICA..