Vadis Password

[rstrang]

>Didn't work for me.
>
>:-( Editted the correct parts of the file, but when Vadis was
>started it didn't change a thing.
>
>Dan.

Hi Dan,

Vadis version 6.3.2465 2003 Edition B -US

My cdinfo.ini below:

[SetupCDInfo]
Cdname=dvdsetus
Status=R
StageDate="2003-04-16"
Volid=VV117063
Title="VADIS 2003 Edition B - US"
Released="2003-04-16"
ValidInfoDate="2003-04-16"
WarningDays=2000
ExpirationDays=2000
DataCompatibilityRev=3
DataCDVolids=VV117042;VV116342;
EMDVrelease="rel660 02/06/20 10:52"
CdSize=332029952

This works for me :-)

Richard

[sholtby]

Is it just my computer or does Vadis take ages to load? ie 2 hours

Simon

[rstrang]

>Is it just my computer or does Vadis take ages to load? ie 2
>hours
>
>Simon

Install took about 45 minutes on my notebook P4@2GHz

Load takes about 2-3 seconds

Richard

[sholtby]

I should have said install. Just checked and my computer is an AMD 800 MHZ which would explain why it takes over twice as long as yours to install.

Thanks

Simon

[Chris139]

Mine took 1hr 10mins to install on a Celeron 1000Mhz. I was warned that it would take about an hour when it came. Great news about the date hack - will try that later.

Chris

[Dan F]

Hi.

Mine is exactly the same version.

I will try again. I did use the values you gave not 2000 for each, so perhaps that is why.
:)

Cheers,
Dan.

[Dan F]

It isn't so much the processor as the speed of the rom drive you are installing it from, the hard disk you are installing it to and your bus speed.

But yes, it does seem to take an Eon doesn't it? Loading is about 2 seconds, but the install was a go away and come back job. ;-)

Dan.

[rstrang]

>Hi.
>
>Mine is exactly the same version.
>
>I will try again. I did use the values you gave not 2000 for
>each, so perhaps that is why.
>:)
>
>Cheers,
>Dan.

I don't think that's the problem 1800 2000 2100 I just added a zero to the end of the standard setup. 2000 runs till some time in 2008 which seemed Ok. to me...

I also tried 0 and -1 to see if there was a 'backdoor' value, neither worked.

You need to check that the file that you are editing is the one that Vadis is using - maybe rename to something else and check that Vadis complains !!!

Richard

[vjck_uk]

That's great Dan,I've done it with mine and that's much better.
Thanks again.
Vaughan

[Dan F]

Hi.

I realised what had happened almost as soon as I had finished my last post....

I had done an aborted install on the first attempt and realised that my C: drive wasn't big enough. I therefore installed it on my D: drive.

I didn't completely delete all associated files when I tried again and I merely editted the wrong file.

So it is done now, and works a treat. ;-)

:)

Dan.