Vienna Symphonic Library Forum
Forum Statistics

181,945 users have contributed to 42,195 threads and 254,636 posts.

In the past 24 hours, we have 5 new thread(s), 13 new post(s) and 51 new user(s).

  1. Home
  2. General & Hardware
  3. VI2 crashes even on a completely fresh XP system

  • VI2 crashes even on a completely fresh XP system

    P
    P

     I don't like this anymore...

    http://community.vsl.co.at/forums/t/20641.aspx (previous topic)

    I have reinstalled XP SP2 on the PC from which I want to run VE2 and VI2's. After installing all the required drivers, including the latest driver for my RME HDSP 9652 sound card, VI2 again crashes as soon as the main window is displayed.

    In the previous topic I already mentioned that the crash is due to the combination of VI/VE and the RME card...

    When I purchased the App. Strings there was not a problem (a previous version of the VI player).

    I have now spent some eight hours on this and it's becoming pretty frustrating. I'm an IT professional, so I know how to handle my hardware and software. All evidence points in the direction of the Vienna software. Please read the previous topic for all the attempts I have made to circumvent this crash.

    I hope VSL will look into this.

    Best,

    Peter
  • P
    P

    Should I contact you via email for support for this? I feel clueless, I mean, a completely clean PC, a professional sound card and just bang, VI2 crashes still. I really hope you can help me with this.

    Best regards,

    Peter Emanuel Roos
  • H
    H

     Hi Peter,

    I think without a crahslog which you could send our supportteam cannot offer any help in this case,

    because this problem is not reproduceable on any of our machines.

    (Maybe damaged RAM modules or something similias causing these problems?)

    best

    Herb
  • P
    P

    Thanks Herb,

    I have sent the required info to support.

    All the best,

    Peter
  • P
    P

     The new updates do not fix my problem [^o)]

    This machine has 3 Gb installed,m but I cannot use the 3GB switch (hal.dll not found problem).

    Could this point to a possible solution? The machine is one in a stack of 6 19" cases, with audio interfaces on top, so it's quite some work to open it up....
  • B
    B

    Was this ever resolved? I'm having the same problem with a RayDat/Mac Pro/Vista64. I can open VE fine so long as I don't try and use the Hammerfall/ASIO driver. If I do it crashes every time. It was fine with a Motu 828, the problem only arose when I installed the RayDat card, although the card appears to work fine with other audio apps.

    So - VE fine with other card, RayDat fine with other apps. RME doesn't have anything on this particular combination, but this thread gives me some hope. Where did it end up?
  • cmC
    VSL Team
    cmC

     hal.dll not found often is a result of a wrong partition entry in the boot.ini - which should look like this

    default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP 3GB" /3GB /USERVA=2000

     

    without a proper hal.dll windows without the /3GB switch shouldn't start either ...

    hth, christian

    and remember: only a CRAY can run an endless loop in just three seconds.
  • cmC
    VSL Team
    cmC
    last edited
    last edited

     

    @bitmit said:

    I can open VE fine so long as I don't try and use the Hammerfall/ASIO driver

    have you already checked the registry for double or wrong value settings for the aux/midi/mixer/wave key in the /drivers32 section?

     

    additionally corrupt asio settings might be the reason - go to C:\Documents and Settings\All Users\ Application Data\VSL\ and delete all ini files from there.

    make sure no vsldaemon is running when doing so (best reboot before) and you must then add sample content locations again using the directory manager.

    hth, christian

    and remember: only a CRAY can run an endless loop in just three seconds.
  • B
    B

    Christian,

    Thanks for a prompt response - I think I even understand some of it :) Would you mind walking me through it, in terms a musician might understand?! I don't know how or where to check/edit the registry settings you mention, and I don't have that file path for the corrupt ini files. Is that analogous to trashing prefs in Mac OS? It seems similar.

    Thanks.
  • B
    B

    Ok, I found Registry editor. There are multiples of midi - i.e. midi1 midi2 etc., and the same for mixer and wave. Do you mean delete those? Also, I can't find the ini files anywhere...
  • cmC
    VSL Team
    cmC
    last edited
    last edited

    please check my post here with a screenshot

    also see here where those .ini files reside, just a german XP here - in VISTA the hierarchy starts at C:\Users\

    (you might need to set your explorer preferences to show all files and file extensions)

    hth, christian

    and remember: only a CRAY can run an endless loop in just three seconds.
  • B
    B

     Thanks for the help. I deleted the redundant registry entries, and also the ini files. One more question - do I delet the path files and vsl ini that are outside the VSL directory itslef i.e. directly in the Program Data directory? I'll attach a screenshot...

    Hm... How do I attach files to this message?
  • cmC
    VSL Team
    cmC

     i did not when i ran into a similar problem ... deleting them might cause the need of a re-install of the software ... i never tried that

    christian

     

    ps: changing registry settings become effective only after a reboot ...

    and remember: only a CRAY can run an endless loop in just three seconds.
  • B
    B

     Doesn't matter - none of it worked anyway. VE still crashes as soon as I try to select the asio hammerfall driver. Any thoughts? Would it help to see a crash log? (You'll have to describe how to do that)
  • cmC
    VSL Team
    cmC

      then it rather looks like a damaged RME driver ... unfortunately i don't have a RayDat card over here to check in detail ...

    i'd recommend to do a clean uninstall of them, check for BIOS updates on the RME site and downloading the latest drivers.

    avoid the old drivers get installed after eventually forced to reboot installing the new ones before the reboot.

    hth, christian

    and remember: only a CRAY can run an endless loop in just three seconds.
  • B
    B

    Re-installing both as we speak. I'm afraid I don't quite understand your last sentence though, can you try it again? (No reflection on your English - it's very good, but I can't quite follow your meaning just there).
  • C
    C

    What he was saying in his last sentence was to make sure that you actually install the new driver before rebooting the machine because if you reboot, windows will most likely automatically try to install the RME for you and it will be forced to use the old driver.  Installing the new driver brefore rebooting will force Windows to install from the new driver only.

    Maestro2be
  • P
    P

    I also did the same, clean XP installation, disabling services I know that are not important (so that XP runs in only 80 MB, like on my GigaStudio machines), again installed the latest RME HDSP drivers and still ran into the same problem. I have actually given up on this a few months ago. I will probabaly try it again without the sound card and try the network approach.

    In my case there were thus no redundant driver instances in the Reg.Maybe I should also try to remove the third Gb RAM stick? This machine is in a stack of heavy 19" cases with my Madi, ADDA and network switch on top, so that's a nasty exercise ;-)

    Cheers
  • B
    B

     I re-installed VE and the RME drivers - no joy. Ended up switching back to the Motu card. I posted on the RME forum also - they have no knowledge/experience of their cards/systems in this particular combination, and as the Vienna team doesn't have a Raydat card it seems I'm out of immediate support options. Thanks for everyone's help all the same.
  • P
    P

    Sad...

    I find it weird, RME are amongst the best audio card and driver developers, and it seems now that there are at least two people who can't run VE with RME - even on completely clean systems. I once sent in the crash log and was told that it might have to do with the number of audio channels. Which I found very weird. An RME HDSP 9652 does not have THAT much channels...? (3 x Adat). An update would fix that problem, well, it didn't, and I have spent more than enought time trying to get my Appasionata Strings to work. I still haven't been able to use them.

    I still prefer to buy samples libs for a solid third party engine (like GigaStudio 3) than this locked, combined samples+player approach. I bought samples, but I simply can't use them. I find that pretty weird.

    My 2 cents