Every Silver Lining Has A Dark Cloud
-
Our accountant informed me yesterday that she managed to get approval for a new computer for me. That's the good news, as my PC sucks. Try running AutoCAD, ESRI ArcInfo, or any small utility from Microsoft on a machine with only 512k RAM sometime. A newer machine would be wonderful, except for one small thing. The complex licensing schemes used by Autodesk and ESRI guarantee at least a week of lost time trying to transfer the software to the new machine. And, like all of you, I'm sure, over the years I've come to depend on numerous little tools that are scattered all over my hard drive for day to day operations. I'm going to have to locate them, find the installers, transfer everything to the new PC, and get them working again. I'm dreading it. Windows is entirely to blame for the complexity of adding a new computer to inventory. Before the inception of a Registry we could simply copy files from one PC to another, maybe add a shortcut to the home directory, and we're back in business. The concept of a central repository for program info was great, but because so much hardware dependent information is embedded in the various hives it is impossible to replicate an old drive on a new PC. Everything has to be reinstalled. I hate it. How long does it typically take you to recover from a hardware upgrade?
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
Roger Wright wrote:
Try running AutoCAD, ESRI ArcInfo, or any small utility from Microsoft on a machine with only 512k RAM sometime.
Sorry to hear about your old computer. But 640K should be enough for anyone. ;) jhaga
How to earn $100/month.
-
Roger Wright wrote:
How long does it typically take you to recover from a hardware upgrade?
Owing to the fact that our previous Accounts Software Package is not transferable from an old machine to a new machine,(previous supplier went tits up and we have no support or checkable product key ability), I am still running a Win98 machine so as to be able to access job cost information! That said, when this machine does cough and splutter it's way to Silicon Heaven I will be in trouble. I can transfer the balances of the various jobs, and can do a hard copy of the details but I'll be buggered if I am going to get one of my staff to spend a week typing in ancient data. (I keep them far too busy at the best of times). All newer stuff transfers over in a day or two, but I have an anal streak when it comes to putting stuff on my PC. (Notes, Records etc.) :)
------------------------------------ "I want you to imagine I have a blaster in my hand" - Zaphod Beeblebrox. "You DO have a blaster in your hand" - Freighter Pilot "Yeah, so you don't have to tax your imagination too hard" - Zaphod Beeblebrox
Dalek Dave wrote:
when this machine does cough and splutter it's way to Silicon Heaven I will be in trouble.
Why? If it's critical to the business, it's backed up, isn't it? If the hardware's dodgy, that's what virtualisation is for.
-
Dalek Dave wrote:
when this machine does cough and splutter it's way to Silicon Heaven I will be in trouble.
Why? If it's critical to the business, it's backed up, isn't it? If the hardware's dodgy, that's what virtualisation is for.
The Actual software is not transferable. If you move it from one machine to another it requires a new, unique, product key, available only from the original software company, which is defunct. The data cannot be accessed any other way. (I have a CSV file and can manipulate some of the data, but it is difficult)
------------------------------------ "I want you to imagine I have a blaster in my hand" - Zaphod Beeblebrox. "You DO have a blaster in your hand" - Freighter Pilot "Yeah, so you don't have to tax your imagination too hard" - Zaphod Beeblebrox
-
The Actual software is not transferable. If you move it from one machine to another it requires a new, unique, product key, available only from the original software company, which is defunct. The data cannot be accessed any other way. (I have a CSV file and can manipulate some of the data, but it is difficult)
------------------------------------ "I want you to imagine I have a blaster in my hand" - Zaphod Beeblebrox. "You DO have a blaster in your hand" - Freighter Pilot "Yeah, so you don't have to tax your imagination too hard" - Zaphod Beeblebrox
Dalek Dave wrote:
it requires a new, unique, product key, available only from the original software company, which is defunct
Oooh. Nasty.
-
Our accountant informed me yesterday that she managed to get approval for a new computer for me. That's the good news, as my PC sucks. Try running AutoCAD, ESRI ArcInfo, or any small utility from Microsoft on a machine with only 512k RAM sometime. A newer machine would be wonderful, except for one small thing. The complex licensing schemes used by Autodesk and ESRI guarantee at least a week of lost time trying to transfer the software to the new machine. And, like all of you, I'm sure, over the years I've come to depend on numerous little tools that are scattered all over my hard drive for day to day operations. I'm going to have to locate them, find the installers, transfer everything to the new PC, and get them working again. I'm dreading it. Windows is entirely to blame for the complexity of adding a new computer to inventory. Before the inception of a Registry we could simply copy files from one PC to another, maybe add a shortcut to the home directory, and we're back in business. The concept of a central repository for program info was great, but because so much hardware dependent information is embedded in the various hives it is impossible to replicate an old drive on a new PC. Everything has to be reinstalled. I hate it. How long does it typically take you to recover from a hardware upgrade?
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
Roger Wright wrote:
I'm going to have to locate them, find the installers, transfer everything to the new PC, and get them working again. I'm dreading it.
But you said you have a week without your big programs running? Use it to install new versions of all the things you Thad. hat was how I did that when I got me new double Xeon a few years ago. Or is your new computer not at your disposal for the whole week? Also, think hard what utilities and tools you have used in the last half a year, and absolutely only install that on the new computer! The other stuff is obviously useless, you will not miss it. Anyway, a windows installation is like a pair of new shoes: you need a few weeks to feel comfortable in it.
Let's think the unthinkable, let's do the undoable, let's prepare to grapple with the ineffable itself, and see if we may not eff it after all.
Douglas Adams, "Dirk Gently's Holistic Detective Agency" -
The Actual software is not transferable. If you move it from one machine to another it requires a new, unique, product key, available only from the original software company, which is defunct. The data cannot be accessed any other way. (I have a CSV file and can manipulate some of the data, but it is difficult)
------------------------------------ "I want you to imagine I have a blaster in my hand" - Zaphod Beeblebrox. "You DO have a blaster in your hand" - Freighter Pilot "Yeah, so you don't have to tax your imagination too hard" - Zaphod Beeblebrox
-
Our accountant informed me yesterday that she managed to get approval for a new computer for me. That's the good news, as my PC sucks. Try running AutoCAD, ESRI ArcInfo, or any small utility from Microsoft on a machine with only 512k RAM sometime. A newer machine would be wonderful, except for one small thing. The complex licensing schemes used by Autodesk and ESRI guarantee at least a week of lost time trying to transfer the software to the new machine. And, like all of you, I'm sure, over the years I've come to depend on numerous little tools that are scattered all over my hard drive for day to day operations. I'm going to have to locate them, find the installers, transfer everything to the new PC, and get them working again. I'm dreading it. Windows is entirely to blame for the complexity of adding a new computer to inventory. Before the inception of a Registry we could simply copy files from one PC to another, maybe add a shortcut to the home directory, and we're back in business. The concept of a central repository for program info was great, but because so much hardware dependent information is embedded in the various hives it is impossible to replicate an old drive on a new PC. Everything has to be reinstalled. I hate it. How long does it typically take you to recover from a hardware upgrade?
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
It takes about a day to be up and running at all, and about two weeks of missing-thingamajick-pain, which is saturated for about 3 days an then starts to decline exponentially. Take it as a chance to reevaluate and update your tools.
Roger Wright wrote:
Windows is entirely to blame for the complexity of adding a new computer to inventory.
It's not just the registry. Program Data? [programfiles]\company\app\ Program Data shared by multiple apps? [commonprogramfiles]\company\ program data that is required, but may be written to by your program? [all users]\application data\company\app\ ...and is user specific? [userprofile]\application data\company\app\ ...but is simply to big to participate in roaming: [userprofile]\local settings\company\app\ The paths have improved in Vista, the confusion has not. I blame the lack of functional install support - And Windows Installer is not what would solve this. It is so navelgazing-obsessed with installation problems, that it doesn't have time for user or (heavens forbid) developer problems.
We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP
blog: TDD - the Aha! | Linkify!| FoldWithUs! | sighist -
The Actual software is not transferable. If you move it from one machine to another it requires a new, unique, product key, available only from the original software company, which is defunct. The data cannot be accessed any other way. (I have a CSV file and can manipulate some of the data, but it is difficult)
------------------------------------ "I want you to imagine I have a blaster in my hand" - Zaphod Beeblebrox. "You DO have a blaster in your hand" - Freighter Pilot "Yeah, so you don't have to tax your imagination too hard" - Zaphod Beeblebrox
That sounds like a major Achilles Heel for your operation. I would think the prudent thing would be to create a transfer mechanism for the data to some other, currently maintained, application ASAP.
Software Zen:
delete this; -
Our accountant informed me yesterday that she managed to get approval for a new computer for me. That's the good news, as my PC sucks. Try running AutoCAD, ESRI ArcInfo, or any small utility from Microsoft on a machine with only 512k RAM sometime. A newer machine would be wonderful, except for one small thing. The complex licensing schemes used by Autodesk and ESRI guarantee at least a week of lost time trying to transfer the software to the new machine. And, like all of you, I'm sure, over the years I've come to depend on numerous little tools that are scattered all over my hard drive for day to day operations. I'm going to have to locate them, find the installers, transfer everything to the new PC, and get them working again. I'm dreading it. Windows is entirely to blame for the complexity of adding a new computer to inventory. Before the inception of a Registry we could simply copy files from one PC to another, maybe add a shortcut to the home directory, and we're back in business. The concept of a central repository for program info was great, but because so much hardware dependent information is embedded in the various hives it is impossible to replicate an old drive on a new PC. Everything has to be reinstalled. I hate it. How long does it typically take you to recover from a hardware upgrade?
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
Installing the apps, 1-2 days. I do have my data and code on a separate disk and backed up so recovering the data is not and issues. I have a question. Is it not possible to take a hard dive (master) from one machine and set it up as a slave on another. This would retain the data and setting for later access if something is missed.
Never underestimate the power of human stupidity RAH
-
Roger Wright wrote:
How long does it typically take you to recover from a hardware upgrade?
Owing to the fact that our previous Accounts Software Package is not transferable from an old machine to a new machine,(previous supplier went tits up and we have no support or checkable product key ability), I am still running a Win98 machine so as to be able to access job cost information! That said, when this machine does cough and splutter it's way to Silicon Heaven I will be in trouble. I can transfer the balances of the various jobs, and can do a hard copy of the details but I'll be buggered if I am going to get one of my staff to spend a week typing in ancient data. (I keep them far too busy at the best of times). All newer stuff transfers over in a day or two, but I have an anal streak when it comes to putting stuff on my PC. (Notes, Records etc.) :)
------------------------------------ "I want you to imagine I have a blaster in my hand" - Zaphod Beeblebrox. "You DO have a blaster in your hand" - Freighter Pilot "Yeah, so you don't have to tax your imagination too hard" - Zaphod Beeblebrox
I would suggest making a Ghost or similar image of the machine as-is. Then if you have to reformat the drive, all the hardware is the same, and you can restore the image. The key should still work. The key is probably looking at the NIC's MAC address for uniqueness. Most of the other hardware could be replaced.
"Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." "There is no one who loves pain itself, who seeks after it and wants to have it, simply because it is pain..."
-
Our accountant informed me yesterday that she managed to get approval for a new computer for me. That's the good news, as my PC sucks. Try running AutoCAD, ESRI ArcInfo, or any small utility from Microsoft on a machine with only 512k RAM sometime. A newer machine would be wonderful, except for one small thing. The complex licensing schemes used by Autodesk and ESRI guarantee at least a week of lost time trying to transfer the software to the new machine. And, like all of you, I'm sure, over the years I've come to depend on numerous little tools that are scattered all over my hard drive for day to day operations. I'm going to have to locate them, find the installers, transfer everything to the new PC, and get them working again. I'm dreading it. Windows is entirely to blame for the complexity of adding a new computer to inventory. Before the inception of a Registry we could simply copy files from one PC to another, maybe add a shortcut to the home directory, and we're back in business. The concept of a central repository for program info was great, but because so much hardware dependent information is embedded in the various hives it is impossible to replicate an old drive on a new PC. Everything has to be reinstalled. I hate it. How long does it typically take you to recover from a hardware upgrade?
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
3-4 days to recover. And I've done it several times from borking my pc at work. Fer Gawd's Sake: Don't forget the LocalData and ApplicationData folders on your old pc. :doh:
"Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." "There is no one who loves pain itself, who seeks after it and wants to have it, simply because it is pain..."
-
Our accountant informed me yesterday that she managed to get approval for a new computer for me. That's the good news, as my PC sucks. Try running AutoCAD, ESRI ArcInfo, or any small utility from Microsoft on a machine with only 512k RAM sometime. A newer machine would be wonderful, except for one small thing. The complex licensing schemes used by Autodesk and ESRI guarantee at least a week of lost time trying to transfer the software to the new machine. And, like all of you, I'm sure, over the years I've come to depend on numerous little tools that are scattered all over my hard drive for day to day operations. I'm going to have to locate them, find the installers, transfer everything to the new PC, and get them working again. I'm dreading it. Windows is entirely to blame for the complexity of adding a new computer to inventory. Before the inception of a Registry we could simply copy files from one PC to another, maybe add a shortcut to the home directory, and we're back in business. The concept of a central repository for program info was great, but because so much hardware dependent information is embedded in the various hives it is impossible to replicate an old drive on a new PC. Everything has to be reinstalled. I hate it. How long does it typically take you to recover from a hardware upgrade?
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
I know how you feel. It takes me about 2-3 weeks to completely rebuild my main machine, reinstalling all of my stuff. From Visual Studio and the relevant other environments and tools to 3D modeling and rendering software and tools to Photoshop and it's crap and all the mail and office tools I use. I dread it every time I upgrade the hardware...
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008 -
Our accountant informed me yesterday that she managed to get approval for a new computer for me. That's the good news, as my PC sucks. Try running AutoCAD, ESRI ArcInfo, or any small utility from Microsoft on a machine with only 512k RAM sometime. A newer machine would be wonderful, except for one small thing. The complex licensing schemes used by Autodesk and ESRI guarantee at least a week of lost time trying to transfer the software to the new machine. And, like all of you, I'm sure, over the years I've come to depend on numerous little tools that are scattered all over my hard drive for day to day operations. I'm going to have to locate them, find the installers, transfer everything to the new PC, and get them working again. I'm dreading it. Windows is entirely to blame for the complexity of adding a new computer to inventory. Before the inception of a Registry we could simply copy files from one PC to another, maybe add a shortcut to the home directory, and we're back in business. The concept of a central repository for program info was great, but because so much hardware dependent information is embedded in the various hives it is impossible to replicate an old drive on a new PC. Everything has to be reinstalled. I hate it. How long does it typically take you to recover from a hardware upgrade?
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
The VmWare physical to virtual tool as really turned the process of upgrading to a new computer on it's head. I've used it and it's simply excellent and entirely free: http://www.vmware.com/products/converter/[^] Use it and you can take as long as you want to slowly get your apps installed to the new computer while still being able to run the old computer much faster on the new computer.
"It's so simple to be wise. Just think of something stupid to say and then don't say it." -Sam Levenson
-
Our accountant informed me yesterday that she managed to get approval for a new computer for me. That's the good news, as my PC sucks. Try running AutoCAD, ESRI ArcInfo, or any small utility from Microsoft on a machine with only 512k RAM sometime. A newer machine would be wonderful, except for one small thing. The complex licensing schemes used by Autodesk and ESRI guarantee at least a week of lost time trying to transfer the software to the new machine. And, like all of you, I'm sure, over the years I've come to depend on numerous little tools that are scattered all over my hard drive for day to day operations. I'm going to have to locate them, find the installers, transfer everything to the new PC, and get them working again. I'm dreading it. Windows is entirely to blame for the complexity of adding a new computer to inventory. Before the inception of a Registry we could simply copy files from one PC to another, maybe add a shortcut to the home directory, and we're back in business. The concept of a central repository for program info was great, but because so much hardware dependent information is embedded in the various hives it is impossible to replicate an old drive on a new PC. Everything has to be reinstalled. I hate it. How long does it typically take you to recover from a hardware upgrade?
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
Roger Wright wrote:
How long does it typically take you to recover from a hardware upgrade?
about two full working days. All the installers I regularly use are in a folder called: common tools. Makes reinstalls a breeze. :) I crash an OS about every 2 years or so, crash it hard, and unrecoverable. I've done it on every OS I have ever had except Vista U64. Give me time.
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
-
Our accountant informed me yesterday that she managed to get approval for a new computer for me. That's the good news, as my PC sucks. Try running AutoCAD, ESRI ArcInfo, or any small utility from Microsoft on a machine with only 512k RAM sometime. A newer machine would be wonderful, except for one small thing. The complex licensing schemes used by Autodesk and ESRI guarantee at least a week of lost time trying to transfer the software to the new machine. And, like all of you, I'm sure, over the years I've come to depend on numerous little tools that are scattered all over my hard drive for day to day operations. I'm going to have to locate them, find the installers, transfer everything to the new PC, and get them working again. I'm dreading it. Windows is entirely to blame for the complexity of adding a new computer to inventory. Before the inception of a Registry we could simply copy files from one PC to another, maybe add a shortcut to the home directory, and we're back in business. The concept of a central repository for program info was great, but because so much hardware dependent information is embedded in the various hives it is impossible to replicate an old drive on a new PC. Everything has to be reinstalled. I hate it. How long does it typically take you to recover from a hardware upgrade?
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
After having to reinstall XP four times in the past six months (turned out to be an incompatibility between nForce4 and SATA) I gotten it down fairly well. The single biggest problem are those applications, like Firefox, which don't have a way to save the current settings. (Office 2003 had a marvelous tool to do this as does Visual Studio 2005.) A big time saver was giving up using a local email client and just using yahoo mail and gmail. The registry has created problems, but they already existed or am I the only one who remembers how programs would pile stuff into system.ini and win.ini? Or stick their .ini file in the windows directory? Or those apps which still insist on placing data in the program directories. And then there were the dongles. Still exist, but aren't nearly as prolific as in years past. And what about software that not only uses a dongle, but node locks to a mac address?
Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke
