Vincula/Loading error?

Keep getting this error below in my status window on startup. The font settings in the vincula dialog does not show. Any help would be greatly appreciated as to what causes these error's.

********************************************************************

-

* /hload: unable to open 'C:\WINDOWS\DESKTOP\=MSN= SCRIPTZ\IMMORTALS\vincula\vfcache.dat' (line 1363, vincula.mrc)

-

********************************************************************

Then when i go to vincula connection menu then tick on change vincula settings i get this error below.

********************************************************************

-

* /write: unable to open 'C:\WINDOWS\DESKTOP\=MSN= SCRIPTZ\IMMORTALS\vincula\vprevgen.html' (line 3042, vincula.mrc)

-

unload vinc

delete the following files

vfchache.dat

vpassport.dat

vincula.ini

and make sure nHTMLn_2.92.dll is in the vincula folder

then go to mirc and reload vincula.mrc

unload vinc

delete the following files

vfchache.dat

vpassport.dat

vincula.ini

 

and make sure nHTMLn_2.92.dll is in the vincula folder

 

then go to mirc and reload vincula.mrc

Although that could fix the problem it isn't likely to.

Normally the "Unable to open <file>" error is given for one of three reasons:

1) You're trying to write to a read-only file or a file protected by the operating system.

2) The file has invalid characters in its name, eg: <>?

3)

The filename is the name of a system device, to demonstrate this try any/all of the following:

/write con.txt x
/write ip.txt x
/write nul.txt x
/write prn.txt x
/write shadow.txt x

wrong tidy, this has happened to me before and what i said fixs it

i had the same prob awhile back i. i delted all the files pertainting to vincula and and then put them back in and restarted and loaded that worked ... (wich is basicly what ozzy said )

Thanks for the Info Ozzy that fixed it.

wrong tidy, this has happened to me before and what i said fixs it

Since your solution worked, deleting the files probably fixed problem number 1) in my post

wrong again tidy,

/hload: unable to open 'C:\WINDOWS\DESKTOP\=MSN= SCRIPTZ\IMMORTALS\vincula\vfcache.dat' (line 1363, vincula.mrc)

This means it is trying to read from a file to load into a hash table and it cant

so its NOT trying to write to a read only or protected file.

glad it worked epox

I was talking about the /write error.

still wrong tidy,

it couldnt do anything cause the link to nhtml dll was wrong

(which is contained in one of the files i told him to delete)

thats why it couldnt write cause it couldnt load the dll in first place , thus there was nothing for it to try and write

so reloading vinc remade the files with the correct paths and thus the dll loaded and he didnt get the write error , because there is now something for it to write

still wrong tidy,

 

it couldnt do anything cause the link to nhtml dll was wrong

(which is contained in one of the files i told him to delete)

 

thats why it couldnt write cause it couldnt load the dll in first place , thus there was nothing for it to try and write

 

so reloading vinc remade the files with the correct paths and thus the dll loaded and he didnt get the write error , because there is now something for it to write

When you only pass the filename to /write it will create a new file if the file doesn't exist and absolutely nothing if it does exist, try it yourself:

/write x
//write x $dll(c:\x)
//write x $null

c:\x is not a dll so your nhtmln theory cannot possibly be right.

Edit: even if mIRC did give an error, it would most likely give an 'insufficient parameters' error rather than an 'unable to open file' one.

I would suggest you keep quiet now tidy , cause at first you said what i did would fix what you said in item number one , which was nothing to do with reading anything

1) You're trying to write to a read-only file or a file protected by the operating system.

Since your solution worked, deleting the files probably fixed problem number 1) in my post

and as much as i would love to carry this on, i just dont have the time, thus the topic is locked as i fixed the problem