Wow its been so many years I even forgot how to spell SCO.I don't think vmware converter has an interface for SCO, so I started wondering if there was a way to take a physical disk and convert it to a vmdk. After a few seconds of googling, I found this There are a few other examples out there using this search phrase 'clonezilla convert to vmware image'Just setup your virtual machine as close as possible (hardware wise) as the original hardware. By using clonezilla you can migrate your image without destroying your original host server. I did something similar a few years ago with ghost, but with an OS2 system. Yep forgot about that too. Well thought I would answer my only problem.I got the nic to finally work.
Here is what I did. After logging into sco I added the network card to the virtual machine through VMWare vSphere. Then after a fresh boot within SCO I ran a netconfig and added the card using the utility.Hardware Add new LAN Adapter.It automatically found a HW AMD PCNet-PCI Adapter Card.
I configured the TCP/IP settings to what I needed. Then exited the utility and it asked to Relink the Kernel, I did that rebooted and the NIC started working. Sorry to leave you guys hanging. I have a full write up somewhere of this process. Jeremy2377 is spot on - that's precisely what we needed to do. I ended up creating a full image of the server using a Damn Small linux boot up CD and pushing it over the network to a SMB share.
I then created a VM and used Damn Small LInux to restore the data from the remote SMB share to a new vmware disk. I needed to find and install some custom drivers for the SCSI controller, network card and printers which were a super pain, but after we got the old drivers cleaned out, it runs Open Accounting pretty solid. Checked on the client a few months ago and they've been running on a new Dell T420 server for about a year now with no problems on VMware ESXi 5.1. I don't know if it is possible to virtualize SCO 3. When I was doing this job last year, everything I was able to find where people had been successful was with 5.0.4, 5.0.5, 5.0.6 and 5.0.7.It is likely that you will need to upgrade to one of these versions prior to being able to virtualize.
I suggest giving SCO a call to see if an upgrade is even possible.If you private message me I can talk with you on the phone about this and see if we can work something out from a consulting perspective. It won't be cheap though.
Dear Stan,Thank you for the post. Would this work on SCO unix 5.07? SCO has released maintanence pack 5 for this and itis supposed to take care of the DST change.
I tried to install it and it crashed my system and I had to remove patch five and reinstall MP four to run Medical Manager office software.How would you modify your solution for central time zone?Thank you again for your continuing inputs. I too verymuch enjoy readint Tek-tips like jimbolya.RE: SCO 5.0.5 Daylight Savings Time Change (MIS) 16 Feb 07 14:22. Eyedoc1975, yes this does work in 5.0.7TZ=CST6CDT,M3.2.0/2,M11.1.0/2what they have changed with mp5 are the 'defaults' for the time changes, whereas this string in /etc/TIMEZONE just overrides them.there is a script called /etc/tz that will set this up for you. The one catch is to say that you are NOT in north america, then all the optional questions show up.5.0.5 on some installations has been a little annoying and i don't know if it is unique to our customers. On some systems the /etc/profile is not actually running /etc/TIMEZONE to include the TZ override. So we just forced it by adding a line in /etc/profile just before the case $0 line. /etc/TIMEZONEthat reads, dot space slash e t c slash T I M E Z O N Eso it is included at the same level, not executed as a sub shell.RE: SCO 5.0.5 Daylight Savings Time Change (TechnicalUser) 26 Feb 07 12:01.
I'm new to this forum so hopefully I'm adding to this thread.I tried what Stan suggested and then tested it. It didn't change when I set the date and time forward to Mar 11, 1:55am. Do you need to do anything else other than run the /etc/tz script?I tested it on a SCO 6 box with MP2. SLS oss706c causes my applications to hang so I can't install it. I used 'asktime' to change the time.Also, I rebooted after I ran /etc/tz and it DID work. I'd like to avoid the rebooting on our other customers if possible.
They are on various flavors of SCO including 3.2v4.2 and 5.0.2 to 5.07. Any thoughts? RE: SCO 5.0.5 Daylight Savings Time Change (MIS) 27 Feb 07 07:44. Bobkattkgif you don't reboot then only the user processes will have the new timezone parameters set and your log files will be very confusing to look at.the daemon processes are ultimately spawned by 'init' and inherit its environment variables.
'init' runs /etc/initscript when it starts and this is where the TZ variable is initially set (if /etc/TIMEZONE is executable.be careful with that).contrary to my earlier post you do not need to change /etc/profile just make sure /etc/TIMEZONE is executable! RE: SCO 5.0.5 Daylight Savings Time Change (IS/IT-Management) 27 Feb 07 07:56. First of all thanks stanhubble for your valuable information. You saved me a lot of headache.I applied your solution and as bobkattkg said, I had to reboot to have it work. Then, on a test system, I modified the /etc/TIMEZONE file and it did not change after adjusting the date and time to march 11, 1:59:30.So I simply typed the TZ=AST4ADT,M3.2.0,M11.1.0 at root command prompt, then export TZ, and it worked without rebooting.Do you see any problem with this stanhubble?
If you do, I will reboot, but if you don't, it saves me spending a few hours at the office in the middle of the night.Again, thanks a lot. RE: SCO 5.0.5 Daylight Savings Time Change (MIS) 27 Feb 07 08:54.