Thanks for that - clearly then this is nothing to do with currupted Install files - your install file works for your Desktop to the point of running the program correctly. Unfortunately I do not have a modern Desktop computer to try it on.

It sounds as if both our laptops are indeed suffering from an identical incompatability problem.

What is your machine? As you've mentioned the Intel 945 chipset twice I guess you know that the chipsets in both our machines are the same? Are they?

Finally, I tried all your suggestions except disabling the Due core - no result as we expected. I could not get DPE to re-enable following the instructions in your link. At the moment I'm just restoring the whole partition from my backup which hopefully will sort that out.

I guess the next question is what do we do now?

Further to the above, I restored the Win 7 installation and re-installed LW 11. This time (and I think it also happened before) when running Lightworks I received a HASP error code H0005 and the run terminated! I had in the meantime reset the BIOS to allow Virtualization and I again disabled this and ran the LW 11 program and now got to the Window of Lightworks loading which again moved across to show the message Checking DDL versions before terminating, this time with the error message (see attachment) I posted previously.

So it would seem that Sentinel HASP is terminating the run with Virtualization present and when removed the termination is somehow to do with a DDL file and the LightWorks Device Manager Driver?

Ian

My laptop is Toshiba Portege R500-126. Unlike original version, I'm running Windows 7 32-bit. It's using Intel 945GMS Express chipset, with GMA 950 graphics core.

There indeed are different versions of 945 chipsets, with slightly different specs. I found a list of the models in trusty ol' Wikipedia. en.wikipedia.org/wiki/List_of_Intel_chipsets#Core.2FCore_2_mobile_chipsets


I haven't got any Sentinel/HASP errors displayed while trying to start Lightworks. It doesn't mean that I do not have a problem with it, just that I'm not getting displayed errors...

Obviously, the load screen is not displayin all and every piece of loading information: There could be something else going on between DLL check and Device Manager Driver initialisation (Sentinel check? Just a guess.), or it could turn out to be something completely different.


EDIT: I forgot to mention, that it could also be a case where we have two separate problems going on, one with system specs / drivers and other with f.ex. Sentinel, and just coincidentally the both happen around the same time loading the program. However this is quite unlikely, I'd say.

Ah, nice to hear I'm not alone on this. I've the same problem as well; Lightworks loads to a hundred percent, flashes the "Checking Dll.." for a split-second, and just goes away. Tried opening it via ntcardvt.exe as well; I could see it using more RAM in Task Manager as the seconds pass after starting it, but it disappears without a trace shortly after.

As for the chipset, it's the.. "G31/G33 Express Chipset Family". Up to date according to Intel's Driver update utility.. 2 GBs worth of RAM and a 2.4 Ghz processor. Definitely not a very suitable set up for a program like this, but meh.

Hi there TheNekoMuslim and Joonasli again. Thanks for the information on the chips sets used for both of you.

Clearly Joonsali has a notebook about 2 years newer than mine but also using a centrino duo set - I believe my Dell Inspiron which I bought in Australia in March 2006 was the first Dell to come out with the Duo 2 core chip? We have a cominality there. Your G31/G33 chipset, is it installed in a desktop machine TheNekoMuslim and it seems to be at least 2 years newer again than ours installed in notebooks?

I'm not sure where I am going with all this as I am REALLY not a technical person at all - merely someone who has become hooked on using, at last, a decent and capable NLE for editing my HD .mov files. Now it looks as if I am stuck between a rock and a hard place - the Beta version of LightWorks has worked brilliantly for me on my only capable notebook and as a retired person on a very limited income I just cannot go out and buy a much newer machine in the hope that it will work at all with LightWorks. We are not even sure, at all that the problems are limited to older laptops as I suspect that the G31/G33 machine is a desktop.

I guess I'll have to hope that the LightWorks boffins will be able to work out what on earth is going on an come up with a upgrade/solution.

Thanks again all who have responded to these posts

Ian

I've found my log file thanks to a posting here:

Lightworks No. 1 : Release Lightworks 11 dated May 25 2012
Starting at Sat Jun 02 05:17:35 2012

Memory : 1.1 Gb / 2.0 Gb
CPUs : 1
Admin : Yes

Setting project base directory C:\Documents and Settings\All Users\Documents\Lightworks\Projects\
D3D9Ex NOT supported
-0.000 : warning : exiting thread mainThread

So, no actual information about why it abandoned loading.

My graphics card is an AGP ATI Radeon 3600 series (can't remember exactly which one), and previously I managed to get Beta 10 to load, although decided to wait until version 11 to do any editing. I specifically picked the graphic card because it had Shader 2.0 that I needed for running Muvizu. Is it inadequate? I can put up with performance issues if that's the only problem with it.

Yes, the chipset's installed in a desktop. But, if by "two years newer again than" your chipsets, you mean when I finally got my hands on the PC? That'll be around.. 2007. The chipset itself was released some time in that year.

When I first downloaded Beta 10 about last August or so, I didn't actually put it to much use. I was only messing around with it at the time without putting much of an effort to really adjust to it and all. I only recently found out that v11 was released. So I had it downloaded and installed, thereby having the orignal working (despite that red Unlicensed message at the bottom) Beta 10 overwritten by the new installation. Tried starting v11 up, and needless to say, I am where I am now..