Guest BlackBird Report post Posted 11/25/2006 08:14 PM Hello!, I just installed an eval copy of VoiceGuide 5.2.5001 with a TAPI device (ZOOM 3025c). I ran the config wiz., then created a sample script, and ran it. After pressing the "Set and Run the current script" I recieved the following message: --------------------------- VoiceGuide --------------------------- Run-time error '71': Disk not ready --------------------------- OK --------------------------- At first I thought that it was my novice script, so I loaded some of the sample scripts and ensure that any path references within the sample scripts point to my local system drive (H:\), where VG was installed. However the error mentioned above re-occurs, I also confirmed the path references within the .ini found in the VG directory. Could you please shed some light into the definition & resolution on the error reported above? Please let me know if you need the log files. Regards, Raf Share this post Link to post
SupportTeam Report post Posted 11/26/2006 09:11 AM Current release of TAPI version of VoiceGuide is 5.0.5049. Please try using that version of VG. Where did you download v5.2.5001 from? Share this post Link to post
Guest BlackBird Report post Posted 11/26/2006 01:16 PM I will proceed to upgrade to the newest version.. BTW, I downloaded v5.2.5001 from your site (download link), about 3 to 4 weeks ago. How frequent is your revision cycle? Cheers, Raf Share this post Link to post
Guest BlackBird Report post Posted 11/26/2006 01:45 PM I just downloaded and installed VG, the problem originally reported persist/reproes consistently. Is it possible that the code has a hard coded path looking at "C:\"? My local OS drive is H:, everything else seems normal. I should have mentioned on my original report that I am using XP SP2. Also, please note that your product versioning seems to inconsistent (code forked?) that is, your site download version for TAPI displays v5.2.5049, however once installed the "About VoiceGuide" button discloses 5.2.5001 Regards, Ralph Share this post Link to post
SupportTeam Report post Posted 11/26/2006 09:35 PM your site download version for TAPI displays v5.2.5049, however once installed the "About VoiceGuide" button discloses 5.2.5001 OK, you're looking at the Script Designer. If you were to start VoiceGuide itself you can then go to the "about" menu and see that the version number is 5.2.5049. The "Disk not ready" error seems to be caused by Windows reporting back to the application that it cannot access the disk on which the particular file is on. Not sure why this error would be happening on your system. Pressing the "Set and Run the current script" button basically sets the current script to be assigned to all the lines devices and starts the VoiceGuide application itself. The same is done in v5.x of VG if you run the Configuration Wizard (or edit the VG.INI directly) and then start the VoiceGuide application. Share this post Link to post
Guest BlackBird Report post Posted 11/28/2006 11:12 PM You are correct, once I was able to launch VoiceGuide then the versioning matches the one you provided below. Please note that before when launching VG or the Config Wizard, I recieved the error mentioned on my original mail, thus neither component was executing. I was able to t.shoot it and fix the problem (see below). It seems that, as I originally suspected, there is a hard path ( for C:\ drive ) in VG's code which seem to be the culprit of the error I encountered. From my original mail, I mentioned that my OS (XP SP2) is installed on "H:" (drive letter), I installed VG on my OS drive under "program files" and the error occured. I then obtained an IDE drive from my lab, installed it as a slave drive, assign it as "C:" drive. I proceed to uninstall the previous version of VG (on "H:") and performed a new installation on "C:" drive. Launched VG, and the error went away - all components are working correctly. I woud expect that VG would install and run from a user defined drive. I found a flurry of other problems, but these are script related and I will post them separately in order to close this incident. thanks again for your follow ups, please let me know if you have any questions with regards to the above findings (I was able to repro the above scenario and the fix on two systems). Regards, Ralph Share this post Link to post
SupportTeam Report post Posted 11/29/2006 08:41 AM We've ran a test here where we installed VoiceGuide v5.2.5049 in directory "F:\NewVg" and then were able to press the "Set and Run the current script" button without any problems. VoiceGuide Script runner started as expected with the current script in Script Editor set as the default script on all lines. Not sure why you are seeing the problems with the "Set and Run the current script" button on your system, but this problem is not really stopping you from using the system as you would still be able to set the current script in v5.x using the VoiceGuide Configuration Wizard instead (or by editing VG.INI file). Share this post Link to post
Guest BlackBird Report post Posted 11/29/2006 01:12 PM Got it, I am not sure as to how your system is setup. To clarify, in my scenario the OS resides on a different drive (other than C:), my OS is installed in H:. If you decide to repro, please ensure that your OS drive is not C:, then install in F: In any event, I am good to go with the fix, so no worries from my end... Share this post Link to post
