PTR SCR

[speed-of-heat]

Hi All,

my spec is below, and I am using 1.0.1b, when i press the PRT SCR button my key board I get an error message DCS.exe - No Disk, There is no hard disk in the Drive. Please insert a disk into drive \Device\Harddisk4\DR

 

 

which then crashes back to the main menu, any ideas?

[Panzertard]

That sounds like DCS doesn't know where to store the images.

This means it may not have all the data it needs for it's installation.

Which means you may have to reinstall - and be sure that you have administrative privleges when install - as well as ensuring that your antivirus/antimalware/antispam systems do not interfere with the installation.

 

Other than that I would have check the general health of my pc if I had that problem (to find more clues about the cause as well).

 

Maybe you do have some crash reports? Check the first post in http://forums.eagle.ru/showthread.php?t=44466 to see how to find it.

[speed-of-heat]

Thanks for the rapid response Panzertard the crash file and error log are at:

 

http://cid-20273372de129cbd.skydrive.live.com/browse.aspx/.Public/DCS%20Crash%20Dump

 

anything obvious before I kick of a chkdsk and reinstall?

[Panzertard]

Oh, and a Dxdiag report too - sorry forgot to request that :)

[speed-of-heat]

done :), its in the same place

[Panzertard]

The only thing I can see that *may* affect the screenshot - altough I dont think it should manifest itself as an error like that is what I found in the Dxdiag;

- ffdshow video encoder,0x00100000,1,1,ffdshow.ax,1.00.0003.1299

It's a 3'rd party video-encoder that may interfere with how DXdiag interpretes the capture in DCS. May. (I'm not that technically qualified to really tell if it is interfering or not).

 

The rest of the video related stuff seems to be vanilla ATI or Win 7.

 

And if you do remember any incidents with your hardware / virus / OS - please tell us, it might be related to your problem :)

[speed-of-heat]

I upgraded my BIOS yesterday so I could install XP mode (I used the latest stable build of the BIOS) , ffdshow has been there for a while

[Panzertard]

I upgraded my BIOS yesterday so I could install XP mode (I used the latest stable build of the BIOS) , ffdshow has been there for a while

So none of thos eshould affect it then.

Screenshot have never worked then?

Are you really sure you have patched your game with the correct language version btw?

Otherwise - I would have tested a uninstall / reinstall.

 

"If you just uninstall Black Shark and then reinstall it again on the same PC without reinstalling your operating system or changing hardware, you do not need to use a deactivation."

[speed-of-heat]

Having done a complete re-install and made incremental changes until i cam duplicate the error, it Seems to be related to multi monitor setup under 1.0.1b, if i am just running with a single monitor config it works fine, only when I have a multi monitor config does it crash when i press PRT SCR

 

I have also posted my lua file's up as well

Edited October 19, 2009 by speed-of-heat

[Panzertard]

Ah, good finding.:thumbup:

So you can confirm that it's an 101b issue only? And it's only a problem with multimonitors?

I'll give the folks a headsup of the issue for the next release :)

[speed-of-heat]

Yup, it might only be a problem with multi-monitor setups of different sizes, i suspect, depends on if you try and prt scr the entire array... I can't see from the lua how you would actually grab the actual physical size of the small monitor (there is no data to support it in the lua per say, only the max width and height of both. Which would cause it try and exceed the physical bounds of the small monitors memory? You can sort of see this behavior in the start up screen for a mission, where the half KA50 image and "bar" is displayed on on monitor but only the KA50 is displayed on the second. My Guess is that adding a attribute for Monitor 1 and 2 (etc...) and then a specific game space (e.g. Monitor 1 + Monitor 2) would solve some this?

 

But I have no way of testing same size monitor setups :) but definately fails on 1.0.1b with my multi monitor setup and did not fail with single monitor setup or under 1.0, to be fair I didn't test 1.0.1a.

Edited October 20, 2009 by speed-of-heat