
how-to block ads
|
|
Share Topic  |
 |
|
|
|
 1 edit | reply to djphoenix
Re: Advice on Networking. Actually in a manufacturing environment, those old systems are not unheard of. I used to work in Manufacturing, and that company had a bunch of old 486's and early model pentiums running equipment. All the computer did was run dos, connect to the network drive, pull csv files and use that decimal data to know how big to cut material. Some of the old controllers freaked out when running faster CPU's. It's like their counters were way off and the systems didn't work. Needless to say we would get old crap at auction for that. I don't work there anymore, but I can understand the use for that ancient equipment in certain situations.
It's really a BIG project you have on your hands. Everything network wise needs to be upgraded. Switches, do some VLAN's, look into metro ethernet WAN links or NxT1's if no fiber is available, domain controller at each location with file & print server and replication, maybe go SAN if the budget allows. Heck now if starting from the ground up, SAN and virtuilization is the way to go. There's a lot of different elements in your assignment that really need attention. Good luck! | |  | said by cypherstream:Actually in a manufacturing environment, those old systems are not unheard of. I used to work in Manufacturing, and that company had a bunch of old 486's and early model pentiums running equipment. All the computer did was run dos, connect to the network drive, pull csv files and use that decimal data to know how big to cut material. Some of the old controllers freaked out when running faster CPU's. It's like their counters were way off and the systems didn't work. Needless to say we would get old crap at auction for that. I don't work there anymore, but I can understand the use for that ancient equipment in certain situations. but they should still plan for new software as it will get harder and harder to find working 486 parts. | |  The Dv8orJust call me Dong Suck Oh, M.D.Premium join:2001-08-09 Denver, CO | said by Joe12345678:said by cypherstream:Actually in a manufacturing environment, those old systems are not unheard of. I used to work in Manufacturing, and that company had a bunch of old 486's and early model pentiums running equipment. All the computer did was run dos, connect to the network drive, pull csv files and use that decimal data to know how big to cut material. Some of the old controllers freaked out when running faster CPU's. It's like their counters were way off and the systems didn't work. Needless to say we would get old crap at auction for that. I don't work there anymore, but I can understand the use for that ancient equipment in certain situations. but they should still plan for new software as it will get harder and harder to find working 486 parts. Now you know why IBM still has a mainframe division. Many companies choose not to upgrade, but rather continue to pour cash into the money pit that is these antiquated systems because somehow it makes more financial sense than putting capital into upgrades. "Buying new" is always a luxury for many of these companies for some ungodly reason. -- You're so vain... I bet you think this post is about you. | | |
|  | reply to cypherstream said by cypherstream:Actually in a manufacturing environment, those old systems are not unheard of. I used to work in Manufacturing, and that company had a bunch of old 486's and early model pentiums running equipment. All the computer did was run dos, connect to the network drive, pull csv files and use that decimal data to know how big to cut material. Some of the old controllers freaked out when running faster CPU's. It's like their counters were way off and the systems didn't work. Needless to say we would get old crap at auction for that. I don't work there anymore, but I can understand the use for that ancient equipment in certain situations. It's really a BIG project you have on your hands. Everything network wise needs to be upgraded. Switches, do some VLAN's, look into metro ethernet WAN links or NxT1's if no fiber is available, domain controller at each location with file & print server and replication, maybe go SAN if the budget allows. Heck now if starting from the ground up, SAN and virtuilization is the way to go. There's a lot of different elements in your assignment that really need attention. Good luck! I have had just that problem, the hole punching software running on dos was coded to the clock speed of the pc. So if pc was faster then 100mhz it would puch holes in the wrong place. | |
|