Vida 2014D Times out 12/31/2017 23:59 Topic is solved

Post by **RickHaleParker** » 23 Dec 2017, 19:49

Has anybody found a way to offset the date in a virtual machine? 2014D expires 12/31/2017 23:59.
I have dedicated hardware with the clock set back to 2014 and no network time and date sync.
I would like to move it to a virtual machine but I know it will time out at the end of the year.

Post by **RickHaleParker** » 26 Dec 2017, 07:30

Shoot ... that was easy enough, once I realized it does not matter if the virtual machine bios date changes. What matter is if Vida sees it change.

This is all done in the virtual machine not on the host.

Install the operating system in the virtual machine, set a password when you create the user.
Disable network time sync.
Create a batch file with one command "Date mm-dd-yy", where mm-dd-yy is date in the past.
Create a Task schedule that will trigger when you log in and run the batch file.
Reboot VM operating system to make sure the date is sticking.

If the date is sticking, Vida will see the date as a never ending day.
Now install Vida on the virtual machine.

I used Date 01-01-14, Vida 2014D installs and will never time out.
If you want, you can now set the user account for automatic login.

Still to do: Get a USB port mapped to the VM.

Post by **scot850** » 01 Jan 2018, 21:57

I have the same problem trying to log into my Vida 2014A and also now 2012 which is in the VM.

I am not a techie/IT guy so any help would be appreciated on how to get around this. I do not have 2014A in VM as it was working fine in MS 7 Pro for the last 3 years.

Neil.

Post by **doublebug** » 02 Jan 2018, 03:16

solution is easy.
Patch is self extracting archive. So
Unpack patch used in previous install and find 3 files.
filldb.cmd
filldb.sql
license

Edit "license" file. It is XML and can be edited with any text editor.
there is string subscriptionExpireDate="2017-12-31 23:59:59"
Set to whatever date you want and run filldb.cmd

That is all.

Post by **scot850** » 02 Jan 2018, 08:20

Many thanks Doublebug! You are a star and your help is appreciated! I will see if I can figure this out but may need more help.

Neil.

Post by **scot850** » 02 Jan 2018, 10:46

Found the file 'license' and changed the date. What I don't know how to do is how to run the filldb.cmb? A little compasion here for a non-computer guy please!

Thanks,

Neil.

Post by **RickHaleParker** » 02 Jan 2018, 11:05

Unpack patch used in previous install and find 3 files.
filldb.cmd
filldb.sql
license

It not as easy as you make it sound.
If I unpack to C:\ these files and patch folder get deleted by 2014A.exe and 2014A-B-D.exe after the patch is run.
If I unpack to a different folder I can get the patch folder and the three files.
I moved the patch folder to C:\Vida and ran filldb.com from the command line. Got a cannot find specific path error.

What would be nice if somebody can make a new patch with the license file edited.

Has anybody else discovered the 2014D RePack comeing out of Russia? It runs native on Windows 7, 8 and 10 with IE11.
The Repack does not have the subscriptionExpireDate fixed in the patch.

Post by **RickHaleParker** » 02 Jan 2018, 18:12

Successfully modified the 2014A patch to extend the subscriptionExpireDate to 2099 23:59:59.
The patch will not enable you run 2014D under windows 10 with IE11. For that your need more then the patch.

Get attached file.

1. Unpack 2014A-B-D-2099.zip file to Desktop.
2. Run 2014A-B-D-2099.exe
3. Install to C:\
4. Reboot and log in to Vida after the icon turns green.

2014A-B-D-2099.zip: (175 KiB) Downloaded 56036 times

I have Vida 2014D running native in Windows 10 E11 in real time in a VM.
Next ... do it on the host just like any other application.

Thanks to Doublebug for showing where to look.

Post by **velorider** » 02 Jan 2018, 18:52

Went to try out my Vida/DICE today for the first time and I could not log into Vida 2014D. I reset the system clock but the system detected that, with a message about the last login date is newer then the system date. So that I don't think is going to work well. I tried the sqldb update on the existing Vida VM but could not get that to work either.

Here are the steps I needed to get mine to work:

1. I reimported the VM, since nothing seems to get the old one to work.
2. Reset the host system clock to ensure it was the date/time issue.
3. Launched Vida VM and confirmed I could log in.
4. Performed the sqldb update
5. Closed the VM
6. Reset the host system clock to the correct time
7. Launched the Vida VM
8. Was able to login

I don't understand way the sqldb update on the original VM wouldn't work.

Good luck!!

Post by **RickHaleParker** » 02 Jan 2018, 19:17

I got 2014D running native in Windows 10 Pro with IE11 ... no VM, no tricks with the clock.
Deleted my VM and Shutdown my remote Vida machine.