Appear to have screwed up 2 different computers with incorrect syntax. Suggestions?

[khelliott]

I'm running Avisyth 2.5 and VirtualDub 1.78

I was learning/experimenting with simple scripts and it appears I've screwed something up badly on two separate computers.
Machine #1: Vista
Machine #2: Windows XP

Simple scripts worked fine at first: I was just loading BMP files using the ImageSource command and then manipulating them. However, when I was ready to load a large HD AVI file, I incorrectly continued to use ImageSource instead of AVISource....something like:
ImageSource("test.avi")
where test.avi is about 20Gb of 10-bit, 1080p, 24Hz HD video

This failed, but I didn't get back to debugging it right away. When I did return, I realized that I was getting the same message on every script.
"Avisynth open failure
Avisynth: script open failed!"
Now, even when I am using the earlier, simple scripts and the BMP file, I still get this error command. I've uninstalled and reinstalled Avisynth and VirtualDub, rebooted multiple times, even performed a system restore and I get the same problem.

When this happened on the first, Vista-based, computer, I didn't notice the incorrect usage of the ImageSource command......I just assumed that it might be a Vista compatibility error (it appears most folks are using XP). I was getting ready to wipe my drive and rebuild it with XP, but I needed to get some work done quickly, so I just moved over to another computer that was already running XP.

This time, I'm 90% certain that the problem started after I ran the incorrect code. Once again,
- the simple BMP files worked fine originally
- I ran the ImageSource command with the AVI file and it didn't work
- Now the simple BMP files don't work either

Once again, rebooting, loading and reloading Avisyth, .....nothing fixes the problem.

I didn't find this topic with a search and my friend (our resident expert) can't figure it out either; he has a vested interest in solving this also, since the 2nd computer I borrowed was actually his. Now, his scripts fail too. Once again, we've rebooted, reloaded, etc.

Both machines are running NTFS, so I thought the size of the file, although large, was still ok.

Any suggestions? (besides don't do that again) :(

[stickboy]

You probably have a malformed .avsi file in your AviSynth plugins directory. Try temporarily moving everything out of your plugins directory, and if that helps, you can gradually move stuff back in until you isolate the problematic file.

[Socio]

Another tip;

If you have multiple .avsi files you might need to change your .avsi files to .avs and then just load the one/ones you need to prevent ones you don't from possibly auto-loading and screwing things up.

[khelliott]

Thanks. This makes a lot of sense. I'm on travel but will check this when I return to the office on Thursday. I'll let you know how it turns out.

[khelliott]

yep, that did it. Had a dash in the function name.