Author Topic: driverlog.txt extremely large  (Read 870 times)

Offline NaughtyN

  • Zinc Member
  • *
  • Posts: 26
driverlog.txt extremely large
« on: June 27, 2009, 07:24:34 AM »
Hello,

i came across this while performing my regular virus scan. I wondered how it could be possible that since my last scan there were 1.5 GB more to scan. I didn't have anything installed.

During my search i cam across a file c:\driverlog.txt which had a huge size of 1.568 GB. I deletet the file an investigatet where it came from.

To my surprise it was created by AH2.

Now my questing, is it normal that the file gets larger and larger, or can a crash of AH2 lead to such a huge driverlog.txt.

And can i change the place were it is store? Would like to safe it in my AH games directory instead of the system drive.

Regards
Naudet

Offline NaughtyN

  • Zinc Member
  • *
  • Posts: 26
Re: driverlog.txt extremely large
« Reply #1 on: June 27, 2009, 11:53:01 AM »
I watched the file driverlog.txt now a while.

After playing AH2 for about 15 Minutes is grew already to 79MB in size again.

To be honest i think there is some kind of bug with das logfile.

Offline The Fugitive

  • Plutonium Member
  • *******
  • Posts: 17705
      • Fugi's Aces Help
Re: driverlog.txt extremely large
« Reply #2 on: June 27, 2009, 01:20:02 PM »
I've been running AH for a couple days now both regular and the new beta and after a search, I can't find a file with that name on my computer. My guess is some other program is generating the file and bloating it. Sounds like a virus to me.

Offline NaughtyN

  • Zinc Member
  • *
  • Posts: 26
Re: driverlog.txt extremely large
« Reply #3 on: June 27, 2009, 01:46:38 PM »
When i delete the file and avoid running AH2, the file is not generated again.

Only after i start AH2 the file is there again.

Here is some of its content:

Current process ID 0x0000097C
DllMain() DLL_PROCESS_ATTACH. ANSI
Entry: DllGetClassObject()
CServerClassFactory::CServerClassFactory()
CServerClassFactory::AddRef() 1
Entry: CServerClassFactory::QueryInterface()
CServerClassFactory::AddRef() 2
Exit: CServerClassFactory::QueryInterface()
CServerClassFactory::Release() 1
Exit: DllGetClassObject()
Entry: CServerClassFactory::CreateInstance()
CFEDriver::CFEDriver()
CFEDriver::Initialize()
Entry: CFEDriver::QueryInterface()
CFEDriver::AddRef() 1
Exit: CFEDriver::QueryInterface()
CFEDriver::Release() 0
Exit: CServerClassFactory::CreateInstance()
CServerClassFactory::Release() 0
CServerClassFactory::~CServerClassFactory()
Entry: CFEDriver::DeviceID()
dwDIVer = 0x00000800
dwExternalID = 0
fBegin = 1
dwInternalId = 0
 mycalloc(): 0, addr=0X03F36EB8,num=8,size=272,
 \\?\hid#vid_04d8&pid_910e#6&275569a9&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
mycalloc(): 1, addr=0X05540DC0,num=5,size=1,
 mycalloc(): 2, addr=0X05540D40,num=1,size=72,
 mycalloc(): 3, addr=0X05540C30,num=3,size=72,
 mycalloc(): 4, addr=0X05541F70,num=4,size=32,
 mycalloc(): 5, addr=0X05540BF0,num=3,size=2,
 mycalloc(): 6, addr=0X05541F40,num=0,size=1,
 mycalloc(): 7, addr=0X05541F10,num=0,size=72,
 mycalloc(): 8, addr=0X05541EE0,num=0,size=72,
 mycalloc(): 9, addr=0X05541EB0,num=0,size=32,
 mycalloc(): 10, addr=0X05541E80,num=0,size=1,
 mycalloc(): 11, addr=0X05541E50,num=0,size=72,
 mycalloc(): 12, addr=0X05541E20,num=0,size=72,
 mycalloc(): 13, addr=0X05541DF0,num=0,size=32,
 \\?\hid#vid_07b5&pid_0317#6&3a68e767&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
mycalloc(): 14, addr=0X05541DB0,num=7,size=1,
 mycalloc(): 15, addr=0X05541D30,num=1,size=72,
 mycalloc(): 16, addr=0X05541B90,num=5,size=72,
 mycalloc(): 17, addr=0X05541AA0,num=6,size=32,
 mycalloc(): 18, addr=0X05541A60,num=8,size=2,
 mycalloc(): 19, addr=0X05541A20,num=5,size=1,
 mycalloc(): 20, addr=0X055419F0,num=0,size=72,
 mycalloc(): 21, addr=0X055418A0,num=4,size=72,
 mycalloc(): 22, addr=0X055417F0,num=4,size=32,
 mycalloc(): 23, addr=0X055417C0,num=0,size=1,
 mycalloc(): 24, addr=0X05541790,num=0,size=72,
 mycalloc(): 25, addr=0X05541760,num=0,size=72,
 mycalloc(): 26, addr=0X05541730,num=0,size=32,
 VendorID=4d8, ProductID=910e
VendorID=7b5, ProductID=317
GetJoyStickID() [szName:\\?\hid#vid_07b5&pid_0317#6&3a68e767&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}]
 Microsoft Windows 2000 or XP.
GetJoyStickID() on Win2000
hid
 vid_07b5&pid_0317
 6&3a68e767&0&0000
 {4d1e55b2-f16f-11cf-88cb-001111000030}
 [szBuf :SYSTEM\CurrentControlSet\Control\DeviceClasses\{4d1e55b2-f16f-11cf-88cb-001111000030}\##?#hid#vid_07b5&pid_0317#6&3a68e767&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\#\Device Parameters\DirectX]
 Fail to get Joystick Id. use 0 as the default value. dwData=0
 Found this joystick (dwExternalID = 0)
myfree():0,1,addr 0X05540DC0
 myfree():1,5,addr 0X05540BF0
 myfree():2,4,addr 0X05541F70
 myfree():3,2,addr 0X05540D40
 myfree():4,3,addr 0X05540C30
 myfree():5,6,addr 0X05541F40
 myfree():6,9,addr 0X05541EB0
 myfree():7,7,addr 0X05541F10
 myfree():8,8,addr 0X05541EE0
 myfree():9,10,addr 0X05541E80
 myfree():10,13,addr 0X05541DF0
 myfree():11,11,addr 0X05541E50
 myfree():12,12,addr 0X05541E20
 myfree():13,14,addr 0X05541DB0
 myfree():14,18,addr 0X05541A60
 myfree():15,17,addr 0X05541AA0
 myfree():16,15,addr 0X05541D30
 myfree():17,16,addr 0X05541B90
 myfree():18,19,addr 0X05541A20
 myfree():19,22,addr 0X055417F0
 myfree():20,20,addr 0X055419F0
 myfree():21,21,addr 0X055418A0
 myfree():22,23,addr 0X055417C0
 myfree():23,26,addr 0X05541730
 myfree():24,24,addr 0X05541790
 myfree():25,25,addr 0X05541760
 myfree():26,0,addr 0X03F36EB8
 szName [\\?\hid#vid_07b5&pid_0317#6&3a68e767&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}]
 device.hDevice = 0x00000400
Entry: CFEDriver::GetVersions()
Entry: CFEDriver::SendForceFeedbackCommand()
dwID = 0
dwCommand = 1
 Command ( DISFFC_RESET )
 DISFFC_RESET
Entry: Eff_FreeList()
Exit: Eff_FreeList() with *pStart = NULL
Entry: MyWaitForSingleObject()
MyWaitForSingleObject():WAIT_OBJECT_0 
Exit: MyWaitForSingleObject()
WriteZero() successfully
Entry: CFEDriver::SetGain()
dwID = 0
dwGain = 10000
 Entry: CFEDriver::SendForceFeedbackCommand()
dwID = 0
dwCommand = 1
 Command ( DISFFC_RESET )
 DISFFC_RESET
Entry: Eff_FreeList()
Exit: Eff_FreeList() with *pStart = NULL
Entry: MyWaitForSingleObject()
MyWaitForSingleObject():WAIT_OBJECT_0 
Exit: MyWaitForSingleObject()
WriteZero() successfully
CFEDriver::Release() -1
CFEDriver::~CFEDriver()
CFEDriver::Exit()
Entry: Eff_FreeList()
Exit: Eff_FreeList() with *pStart = NULL
Entry: MyWaitForSingleObject()
MyWaitForSingleObject():WAIT_OBJECT_0 
Exit: MyWaitForSingleObject()
WriteZero() successfully
device.pStartEffList = 0x00000000
DllMain() DLL_PROCESS_DETACH
Entry: ProcessDetach()
mycalloc(): 27, addr=0X03F36EB8,num=8,size=272,
 \\?\hid#vid_04d8&pid_910e#6&275569a9&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
mycalloc(): 28, addr=0X05540F40,num=5,size=1,
 mycalloc(): 29, addr=0X05540EC0,num=1,size=72,
 mycalloc(): 30, addr=0X05540DB0,num=3,size=72,
 mycalloc(): 31, addr=0X05540D00,num=4,size=32,
 mycalloc(): 32, addr=0X05540CC0,num=3,size=2,
 mycalloc(): 33, addr=0X05540C90,num=0,size=1,
 mycalloc(): 34, addr=0X05540C60,num=0,size=72,
 mycalloc(): 35, addr=0X05540C30,num=0,size=72,
 mycalloc(): 36, addr=0X05540C00,num=0,size=32,
 mycalloc(): 37, addr=0X05541FF0,num=0,size=1,
 mycalloc(): 38, addr=0X05541FC0,num=0,size=72,
 mycalloc(): 39, addr=0X05541F90,num=0,size=72,
 mycalloc(): 40, addr=0X05541F60,num=0,size=32,
 \\?\hid#vid_07b5&pid_0317#6&3a68e767&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
mycalloc(): 41, addr=0X05541F20,num=7,size=1,
 mycalloc(): 42, addr=0X05541EA0,num=1,size=72,
 mycalloc(): 43, addr=0X05541D00,num=5,size=72,
 mycalloc(): 44, addr=0X05541C10,num=6,size=32,
 mycalloc(): 45, addr=0X05541BD0,num=8,size=2,
 mycalloc(): 46, addr=0X05541B90,num=5,size=1,
 mycalloc(): 47, addr=0X05541B60,num=0,size=72,
 mycalloc(): 48, addr=0X05541A10,num=4,size=72,
 mycalloc(): 49, addr=0X05541960,num=4,size=32,
 mycalloc(): 50, addr=0X05541930,num=0,size=1,
 mycalloc(): 51, addr=0X05541900,num=0,size=72,
 mycalloc(): 52, addr=0X055418D0,num=0,size=72,
 mycalloc(): 53, addr=0X055418A0,num=0,size=32,
 ProcessDetach() to WriteZero
 
WriteZero() unsuccessfully
myfree():27,1,addr 0X05540F40
 myfree():28,5,addr 0X05540CC0
 myfree():29,4,addr 0X05540D00
 myfree():30,2,addr 0X05540EC0
 myfree():31,3,addr 0X05540DB0
 myfree():32,6,addr 0X05540C90
 myfree():33,9,addr 0X05540C00
 myfree():34,7,addr 0X05540C60
 myfree():35,8,addr 0X05540C30
 myfree():36,10,addr 0X05541FF0
 myfree():37,13,addr 0X05541F60
 myfree():38,11,addr 0X05541FC0
 myfree():39,12,addr 0X05541F90
 myfree():40,14,addr 0X05541F20
 myfree():41,18,addr 0X05541BD0
 myfree():42,17,addr 0X05541C10
 myfree():43,15,addr 0X05541EA0
 myfree():44,16,addr 0X05541D00
 myfree():45,19,addr 0X05541B90
 myfree():46,22,addr 0X05541960
 myfree():47,20,addr 0X05541B60
 myfree():48,21,addr 0X05541A10
 myfree():49,23,addr 0X05541930
 myfree():50,26,addr 0X055418A0
 myfree():51,24,addr 0X05541900
 myfree():52,25,addr 0X055418D0
 myfree():53,0,addr 0X03F36EB8
 Exit: ProcessDetach()


The text in the file indicates it is searching for the joystickID but failed to find it.


EDIT: Ok, apologize to HT an AH2 crew. The file is created by the driver of one of the joysticks. I could also created it by selecting the Joystick in the game controllers tab of windows. Seems the driver doesn't get the right Joystick ID. But interestingly it works.

« Last Edit: June 27, 2009, 04:34:36 PM by NaughtyN »

Offline -sudz-

  • Nickel Member
  • ***
  • Posts: 609
Re: driverlog.txt extremely large
« Reply #4 on: June 29, 2009, 09:09:59 AM »
This is not generated by AH2.  My guess is that you got a debug or beta version of your video driver installed.

As a test, note the size of (or delete) the driverlog.txt file and then run some other game than AH2.  My guess is that it will expand with the other game as well.   If that's the case you may want to download the latest driver for your card.

- sudz

Offline NaughtyN

  • Zinc Member
  • *
  • Posts: 26
Re: driverlog.txt extremely large
« Reply #5 on: June 29, 2009, 11:41:15 AM »
As i wrote in my EDIT, i found what is creating the logfile.

Its the driver of my joystick. I can create it by using my joystick from systems->gamecontrols. If i uninstall the driver the file is no longer generated, but than i have no force feedback effects. Reinstallation hat no effect so far.
I already contacted the support of the joystick manufacturer.

Offline NaughtyN

  • Zinc Member
  • *
  • Posts: 26
Re: driverlog.txt extremely large
« Reply #6 on: June 30, 2009, 06:57:45 AM »
So i got a first reply of the joystick manufacturer (Speedlink).

It is normal that the speedlink joystick drivers create the driverlog.txt and the size of the file depends on the game played. But a size of more than 100MB is rarely seen. The support asked for the played game and will further investigate the issue.