84 réponses à ce sujet

[joey_mork84]

Like I said, it very well could be a mod, but I really don't see how the Extra Dog Slot mod or similar ones would effect Stealing.. The chances are highly unlikely.

[zartan88]

It could depend on who did the mod, I know one person sorted the dog 'find bug' (this is the same as the stealing bug which states something has been added to your inventory and nothing is.) as well as the 'stealing' bug its possible that he/she combined the two.



If you are running any mods its impossible to state for sure that one of them is'nt fixing the problem.

Remember that if you start again with a new character and fresh install - steal works perfectly around five to six times before you start getting 'Stealing Success' with nothing (items not money) added to your inventory.

[Taritu]

Victor Wachter wrote...

As I said in my sticky, we will be gathering technical information to address performance and stability issues soon. We are working with QA and development to get a format for providing information on this that is as useful as possible and provides at-a-glance information that we can use to help out either on a support level (assisting people to work out issues) or on a development level (creating an update). It will come, it's just not here yet.

And yes, there are way too many stickies on this forum. My task for today is creating an index to be one of far fewer stickies. The message that I want to send is that my goal is to step up BioWare participation in the Tech forums. I read every day and discuss issues with the team, but I want to make it more visible to the community that they are being heard. Asking for information to be presented in a certain way will help me ensure that I understand everything and send it to the rest of the team.

Making that clear would be a good thing ™.  It feels like we're screaming into the wind, and that very old issues haven't been resolved, while patches create new issues.  Just acknowledging the issues (for example, the pickpocket bug) and stating that you're working on them (or not) would go a long way to reducing heartburn amongst fans.

Communicate.  Please.

[joey_mork84]

zartan88 wrote...

Remember that if you start again with a new character and fresh install - steal works perfectly around five to six times before you start getting 'Stealing Success' with nothing (items not money) added to your inventory.

I've used stealing dozens of times on new and old characters today (since this convo started to test these things) and get the 'Stealing Success' message while getting random items as well as money (which is the way its suppose to work, or has for me since I started playing). So, no, I have not experienced this bug. The only real bug I've ever encountered was the game breaking Orzammar bug that everyone has stumbled across at least once.

[Andari_Surana]

Surango and Nukenin have identified the cause of the stealing problem stemming from faulty logic in the script, and posted mods that fix it. Above poster clearly has a mod that incorporates one of the stealing fixes that are circulating. Because said poster has a mod affecting dog (among other unstated mods), and dog cannot digup random items post 1.03, without a mod fix.  The maker of above-poster's dog mod likely overrided the code to produce random-gen items.

The bug is not system dependent, anymore than an If-then-else condition is going to be system dependent.
API calls to render graphics and what not are going to be system dependent.  Basic arithmetic, logic statements, and even the use of system.random are not going to be system dependent.  Even if someones system is highly unstable it must produce the correct result 99.99...% of the time to queries like these to be even bootable.

Modifié par Andari_Surana, 10 avril 2010 - 05:07 .

[Kastagir]

Just a note to those that are not familiar with how software testing works. More than 2/3 of reported issues turn out not to be bugs (this figure is conservative and is probably much higher), but instead caused by other issues such as device drivers, system environment (OS or hardware) - issues that can not be addressed viably by the developer on a per-user basis. If people list their system specs with detailed reproduction steps, the QA people can determine why these things are happening and hunt down the fix. I have no idea why Bioware didn't step up on March 16th to drive this but now that they have, simply complaining about the problems will not be productive. Let's provide bug reports that are as detailed as possible so that even a chimpanzee can reproduce them in testing.

Another key to software testing is to test under a clean environment.  This means to disable/remove any mods before reproducing your issue.  Bioware isn't going to concentrate their effort chasing down issues that might be related to one of the 99 mods you have installed - nor should they.  Failure to at least list the mods you're using is tantamount to filing a false bug report, as is reporting that the game "works fine" without listing any mods you have installed that might address current issues.  Let's try to be accurate in the information that we provide and hopefully Bioware can turn out an update in a reasonable time frame.

Modifié par Kastagir, 10 avril 2010 - 05:09 .

[chickenM]

I can't update my DAO.. It keep asking me to reinstall the game. Any idea? T_T'

[wolfwarp]

joey_mork84 wrote...

I, personally, am just so tired of hearing people saying "Patch 1.03 for DA:O sucks! Don't get it, its full of problems!".. It obviously varies from system to system and person to person since everyone is having different problems. I have not had a single problem with the game since getting patch 1.03, so therefore, saying "The patch is broken and full of bugs" is entirely inaccurate.

Now that I'm done ranting for the moment.. What Gorath has said is right, you need to remember to list your system specs with the fill-in-the-blank form above, along with listing all mods you have installed as some of them can cause issues with the new patch.

Seriously, are you reading the forum on these pain that people are suffering or not?  I personally have posted a number of Windows error reports onto this forum.  No news from the developers.  Sure, give us a format, even better, a tool and we are happy to copy and paste the error messages onto this forum.  I still have tons of errors on my Windows event log.  But I am just so tired of posting errors and see no results.

[SirPalamedes]

I created this thread social.bioware.com/forum/1/topic/58/index/1633999/1 to promote awareness and uncover some of the main bugs with patch 1.03 and to see whether the problems were consistent across different systems. They are, although those with more RAM have to play longer before the slowdowns and crashes really become an issue, which is indicative of a memory leak.

I was simply waiting for Bioware to acknowledge the issues people were having with this new patch and let us know that they were doing something about it.

That Bioware has not been involved is evidenced by the fact that after a month and 880+ reports in my thread there hasn't been any official validation that there is a problem.

Modifié par SirPalamedes, 10 avril 2010 - 12:21 .

[wolfwarp]

Eurypterid wrote...

DeadJediJamie wrote...
That thread is a mess, if they're going to gather information they're going to need to create a separate thread with nothing but system specs and bug reports. No dev is going to sit there and read all that.

That's why I tried to get people to report their system sopecs and other info in that thread. Alas, it didn't work out as I had hoped. I probably should have gone through and deleted any posts that didn't actually report bugs and provide system info, but I'm reluctant to do something like that. Perhaps this new format that Victor mentioned will end up being more useful to the devs.

OK, I am re-posting the log again.  Hope that this time round something can be done, my friend.  Let me know if you want anything else.

EDIT: Retail version (not digital).  Game crashed to Windows.  No mods, only official DLCs.  Random crashes.  It could be during combat, walking around, area transit, or talking to people in the game.


DAO ERROR LOGS (SELECTED)
==========================

Log Name:      Application
Source:        Application Error
Date:          22/2/2010 6:23:42 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      classic
User:          N/A
Computer:     
Description:
Faulting application DAOrigins.exe, version 1.2.9393.0, time stamp 0x4b171181, faulting module DAOrigins.exe, version 1.2.9393.0, time stamp 0x4b171181, exception code 0xc0000005, fault offset 0x000bbbe3, process id 0x1074, application start time 0x01cab399be61b8e0.
Event Xml:

 
   
    1000
    2
    100
    0x80000000000000
   
    42239
    Application
    Kilda
   
 
 
    DAOrigins.exe
    1.2.9393.0
    4b171181
    DAOrigins.exe
    1.2.9393.0
    4b171181
    c0000005
    000bbbe3
    1074
    01cab399be61b8e0
 


Log Name:      Application
Source:        Application Error
Date:          22/2/2010 6:23:37 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      classic
User:          N/A
Computer:     
Description:
Faulting application DAOrigins.exe, version 1.2.9393.0, time stamp 0x4b171181, faulting module DAOrigins.exe, version 1.2.9393.0, time stamp 0x4b171181, exception code 0xc0000005, fault offset 0x0019779e, process id 0x1074, application start time 0x01cab399be61b8e0.
Event Xml:

 
   
    1000
    2
    100
    0x80000000000000
   
    42238
    Application
    Kilda
   
 
 
    DAOrigins.exe
    1.2.9393.0
    4b171181
    DAOrigins.exe
    1.2.9393.0
    4b171181
    c0000005
    0019779e
    1074
    01cab399be61b8e0
 


Log Name:      Application
Source:        Application Error
Date:          16/3/2010 11:25:32 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      classic
User:          N/A
Computer:     
Description:
Faulting application DAOrigins.exe, version 1.3.11253.0, time stamp 0x4b70580a, faulting module DAOrigins.exe, version 1.3.11253.0, time stamp 0x4b70580a, exception code 0xc0000005, fault offset 0x0041bc64, process id 0x16c4, application start time 0x01cac51949787d0a.
Event Xml:

 
   
    1000
    2
    100
    0x80000000000000
   
    44727
    Application
    Kilda
   
 
 
    DAOrigins.exe
    1.3.11253.0
    4b70580a
    DAOrigins.exe
    1.3.11253.0
    4b70580a
    c0000005
    0041bc64
    16c4
    01cac51949787d0a
 


Log Name:      Application
Source:        Application Error
Date:          19/3/2010 11:21:36 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      classic
User:          N/A
Computer:     
Description:
Faulting application DAOrigins.exe, version 1.3.11253.0, time stamp 0x4b70580a, faulting module DAOrigins.exe, version 1.3.11253.0, time stamp 0x4b70580a, exception code 0xc0000005, fault offset 0x0041bc64, process id 0x3c8, application start time 0x01cac77536f7c8f0.
Event Xml:

 
   
    1000
    2
    100
    0x80000000000000
   
    45319
    Application
    Kilda
   
 
 
    DAOrigins.exe
    1.3.11253.0
    4b70580a
    DAOrigins.exe
    1.3.11253.0
    4b70580a
    c0000005
    0041bc64
    3c8
    01cac77536f7c8f0
 



DIRECTX REPORT
===============

------------------
System Information
------------------
Time of this report: 4/10/2010, 20:20:18
       Machine name: KILDA
   Operating System: Windows Vista™ Home Premium (6.0, Build 6002) Service Pack 2 (6002.vistasp2_gdr.091208-0542)
           Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
       System Model: EP35-DS3
               BIOS: Award Modular BIOS v6.00PG
          Processor: Intel® Core™2 Quad  CPU   Q9450  @ 2.66GHz (4 CPUs), ~2.7GHz
             Memory: 3326MB RAM
          Page File: 1498MB used, 5355MB available
        Windows Dir: C:\\\\Windows
    DirectX Version: DirectX 11
DX Setup Parameters: Not found
     DxDiag Version: 7.00.6002.18107 32bit Unicode
------------
DxDiag Notes
------------
      Display Tab 1: No problems found.
        Sound Tab 1: The file ctaud2k.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL).  You may be able to get a WHQL logo'd driver from the hardware manufacturer.
        Sound Tab 2: The file ctaud2k.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL).  You may be able to get a WHQL logo'd driver from the hardware manufacturer.
          Input Tab: No problems found.
--------------------
DirectX Debug Levels
--------------------
Direct3D:    0/4 (retail)
DirectDraw:  0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay:  0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow:  0/6 (retail)
---------------
Display Devices
---------------
        Card name: ATI Radeon HD 5800 Series
     Manufacturer: ATI Technologies Inc.
        Chip type: ATI display adapter (0x6899)
         DAC type: Internal DAC(400MHz)
       Device Key: Enum\\\\PCI\\\\VEN_1002&DEV_6899&SUBSYS_29701682&REV_00
   Display Memory: 2414 MB
 Dedicated Memory: 1015 MB
    Shared Memory: 1399 MB
     Current Mode: 1920 x 1200 (32 bit) (60Hz)
          Monitor: SyncMaster 2433(BWPlus/GWPlus),Magic 2433GWPLUS(Digital)
      Driver Name: atiu9pag.dll,aticfx32.dll,aticfx32.dll,atiumdag.dll,atidxx32.dll,atiumdva.cap
   Driver Version: 8.14.0001.6095 (English)
      DDI Version: 11
   BGRA Supported: Yes
Driver Attributes: Final Retail
 Driver Date/Size: 2/3/2010 11:22:58, 20480 bytes
      WHQL Logo'd: Yes
  WHQL Date Stamp:
Device Identifier: {D7B71EE2-2BD9-11CF-FD62-7109A1C2C535}
        Vendor ID: 0x1002
        Device ID: 0x6899
        SubSys ID: 0x29701682
      Revision ID: 0x0000
      Revision ID: 0x0000
      Video Accel: ModeMPEG2_A ModeMPEG2_C
 Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
                   {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                   {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
                   {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                   {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                   {3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
                   {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                   {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                   {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                   {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                   {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                   {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                   {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
     DDraw Status: Enabled
       D3D Status: Enabled
       AGP Status: Enabled
-------------
Sound Devices
-------------
            Description: Speakers (Creative SB X-Fi)
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: PCI\\\\VEN_1102&DEV_0005&SUBSYS_00311102&REV_00
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: ctaud2k.sys
         Driver Version: 6.00.0001.1373 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: No
          Date and Size: 6/4/2009 02:47:14, 526232 bytes
            Other Files:
        Driver Provider: Creative
         HW Accel Level: Basic
              Cap Flags: 0xF1F
    Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
 Static/Strm HW 3D Bufs: 0, 0
              HW Memory: 0
       Voice Management: No
 EAX™ 2.0 Listen/Src: No, No
   I3DL2™ Listen/Src: No, No
Sensaura™ ZoomFX™: No
            Description: SPDIF Out (Creative SB X-Fi)
 Default Sound Playback: No
 Default Voice Playback: No
            Hardware ID: PCI\\\\VEN_1102&DEV_0005&SUBSYS_00311102&REV_00
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: ctaud2k.sys
         Driver Version: 6.00.0001.1373 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: No
          Date and Size: 6/4/2009 02:47:14, 526232 bytes
            Other Files:
        Driver Provider: Creative
         HW Accel Level: Basic
              Cap Flags: 0xF1F
    Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
 Static/Strm HW 3D Bufs: 0, 0
              HW Memory: 0
       Voice Management: No
 EAX™ 2.0 Listen/Src: No, No
   I3DL2™ Listen/Src: No, No
Sensaura™ ZoomFX™: No
---------------------
Sound Capture Devices
---------------------
            Description: "What U Hear" (Creative SB X-Fi)
  Default Sound Capture: Yes
  Default Voice Capture: Yes
            Driver Name: ctaud2k.sys
         Driver Version: 6.00.0001.1373 (English)
      Driver Attributes: Final Retail
          Date and Size: 6/4/2009 02:47:14, 526232 bytes
              Cap Flags: 0x1
           Format Flags: 0xFFFFF
            Description: Auxiliary (Creative SB X-Fi)
  Default Sound Capture: No
  Default Voice Capture: No
            Driver Name: ctaud2k.sys
         Driver Version: 6.00.0001.1373 (English)
      Driver Attributes: Final Retail
          Date and Size: 6/4/2009 02:47:14, 526232 bytes
              Cap Flags: 0x1
           Format Flags: 0xFFFFF
            Description: Microphone (Creative SB X-Fi)
  Default Sound Capture: No
  Default Voice Capture: No
            Driver Name: ctaud2k.sys
         Driver Version: 6.00.0001.1373 (English)
      Driver Attributes: Final Retail
          Date and Size: 6/4/2009 02:47:14, 526232 bytes
              Cap Flags: 0x1
           Format Flags: 0xFFFFF
            Description: Line-In (Creative SB X-Fi)
  Default Sound Capture: No
  Default Voice Capture: No
            Driver Name: ctaud2k.sys
         Driver Version: 6.00.0001.1373 (English)
      Driver Attributes: Final Retail
          Date and Size: 6/4/2009 02:47:14, 526232 bytes
              Cap Flags: 0x1
           Format Flags: 0xFFFFF
-------------------
DirectInput Devices
-------------------
      Device Name: Mouse
         Attached: 1
    Controller ID: n/a
Vendor/Product ID: n/a
        FF Driver: n/a
      Device Name: Keyboard
         Attached: 1
    Controller ID: n/a
Vendor/Product ID: n/a
        FF Driver: n/a
      Device Name: Controller (XBOX 360 For Windows)
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x045E, 0x028E
        FF Driver: n/a
      Device Name: Microsoft® 2.4GHz Transceiver V2.0
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x045E, 0x071F
        FF Driver: n/a
      Device Name: USB Keyboard
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x04D9, 0x1603
        FF Driver: n/a
      Device Name: USB Keyboard
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x04D9, 0x1603
        FF Driver: n/a
Poll w/ Interrupt: No
-----------
USB Devices
-----------
+ USB Root Hub
| Vendor/Product ID: 0x8086, 0x2939
| Matching Device ID: usb\\\\root_hub
| Service: usbhub
| Driver: usbhub.sys, 4/11/2009 12:43:16, 196096 bytes
| Driver: usbd.sys, 1/21/2008 10:23:03, 5888 bytes
----------------
Gameport Devices
----------------
------------
PS/2 Devices
------------
+ HID Keyboard Device
| Vendor/Product ID: 0x04D9, 0x1603
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
| Driver: kbdhid.sys, 4/11/2009 12:38:40, 17408 bytes
| Driver: kbdclass.sys, 1/21/2008 10:23:23, 35384 bytes
|
+ Terminal Server Keyboard Driver
| Matching Device ID: root\\\\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
| Driver: i8042prt.sys, 1/21/2008 10:23:20, 54784 bytes
| Driver: kbdclass.sys, 1/21/2008 10:23:23, 35384 bytes
|
+ Microsoft USB Wireless Mouse (IntelliPoint)
| Vendor/Product ID: 0x045E, 0x071F
| Matching Device ID: hid\\\\vid_045e&pid_071f&col02
| Upper Filters: Point32
| Service: mouhid
| Driver: point32k.sys, 6/1/2009 13:51:54, 30088 bytes
| Driver: mouhid.sys, 1/21/2008 10:23:20, 15872 bytes
| Driver: mouclass.sys, 1/21/2008 10:23:20, 34360 bytes
|
+ Terminal Server Mouse Driver
| Matching Device ID: root\\\\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
| Driver: termdd.sys, 4/11/2009 14:32:52, 53224 bytes
| Driver: sermouse.sys, 1/21/2008 10:23:20, 19968 bytes
| Driver: mouclass.sys, 1/21/2008 10:23:20, 34360 bytes
------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 203.9 GB
Total Space: 476.9 GB
File System: NTFS
      Model: Hitachi HDP725050GLA360 ATA Device
      Drive: D:
 Free Space: 53.9 GB
Total Space: 382.7 GB
File System: NTFS
      Model: WDC WD5000AAKS-65A7B0 ATA Device
      Drive: F:
 Free Space: 22.2 GB
Total Space: 61.4 GB
File System: NTFS
      Model: WDC WD5000AAKS-65A7B0 ATA Device
      Drive: G:
 Free Space: 25.5 GB
Total Space: 32.8 GB
File System: NTFS
      Model: WDC WD5000AAKS-65A7B0 ATA Device
      Drive: J:
 Free Space: 338.0 GB
Total Space: 953.9 GB
File System: NTFS
      Model: Maxtor OneTouch USB Device
      Drive: Z:
      Model: HL-DT-ST DVDRAM GH20NS10 ATA Device
     Driver: c:\\\\windows\\\\system32\\\\drivers\\\\cdrom.sys, 6.00.6002.18005 (English), 4/11/2009 12:39:17, 67072 bytes
--------------
System Devices
--------------
     Name: Intel® G33/G31/P35/P31 Express Chipset PCI Express Root Port - 29C1
Device ID: PCI\\\\VEN_8086&DEV_29C1&SUBSYS_50001458&REV_02\\\\3&13C0B0C5&2&08
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\pci.sys, 6.00.6002.18005 (English), 4/11/2009 14:32:55, 149480 bytes
     Name: Intel® G33/G31/P35/P31 Express Chipset Processor to I/O Controller - 29C0
Device ID: PCI\\\\VEN_8086&DEV_29C0&SUBSYS_50001458&REV_02\\\\3&13C0B0C5&2&00
   Driver: n/a
     Name: Intel® ICH9 Family PCI Express Root Port 5 - 2948
Device ID: PCI\\\\VEN_8086&DEV_2948&SUBSYS_50011458&REV_02\\\\3&13C0B0C5&2&E4
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\pci.sys, 6.00.6002.18005 (English), 4/11/2009 14:32:55, 149480 bytes
     Name: Intel® ICH9 Family PCI Express Root Port 4 - 2946
Device ID: PCI\\\\VEN_8086&DEV_2946&SUBSYS_50011458&REV_02\\\\3&13C0B0C5&2&E3
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\pci.sys, 6.00.6002.18005 (English), 4/11/2009 14:32:55, 149480 bytes
     Name: Intel® ICH9 Family PCI Express Root Port 1 - 2940
Device ID: PCI\\\\VEN_8086&DEV_2940&SUBSYS_50011458&REV_02\\\\3&13C0B0C5&2&E0
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\pci.sys, 6.00.6002.18005 (English), 4/11/2009 14:32:55, 149480 bytes
     Name: Intel® ICH9 Family USB2 Enhanced Host Controller - 293C
Device ID: PCI\\\\VEN_8086&DEV_293C&SUBSYS_50061458&REV_02\\\\3&13C0B0C5&2&D7
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbehci.sys, 6.00.6002.18005 (English), 4/11/2009 12:42:52, 39936 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbport.sys, 6.00.6002.18005 (English), 4/11/2009 12:42:57, 226304 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbhub.sys, 6.00.6002.18005 (English), 4/11/2009 12:43:16, 196096 bytes
   Driver: C:\\\\Windows\\\\system32\\\\hccoin.dll, 6.00.6000.16386 (English), 11/2/2006 17:46:05, 8704 bytes
   Driver: C:\\\\Windows\\\\system32\\\\hcrstco.dll, 6.00.6001.18000 (English), 1/21/2008 10:23:03, 15872 bytes
     Name: Intel® ICH9 Family USB2 Enhanced Host Controller - 293A
Device ID: PCI\\\\VEN_8086&DEV_293A&SUBSYS_50061458&REV_02\\\\3&13C0B0C5&2&EF
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbehci.sys, 6.00.6002.18005 (English), 4/11/2009 12:42:52, 39936 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbport.sys, 6.00.6002.18005 (English), 4/11/2009 12:42:57, 226304 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbhub.sys, 6.00.6002.18005 (English), 4/11/2009 12:43:16, 196096 bytes
   Driver: C:\\\\Windows\\\\system32\\\\hccoin.dll, 6.00.6000.16386 (English), 11/2/2006 17:46:05, 8704 bytes
   Driver: C:\\\\Windows\\\\system32\\\\hcrstco.dll, 6.00.6001.18000 (English), 1/21/2008 10:23:03, 15872 bytes
     Name: Intel® ICH9 Family USB Universal Host Controller - 2939
Device ID: PCI\\\\VEN_8086&DEV_2939&SUBSYS_50041458&REV_02\\\\3&13C0B0C5&2&D2
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbuhci.sys, 6.00.6001.18000 (English), 1/21/2008 10:23:03, 23552 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbport.sys, 6.00.6002.18005 (English), 4/11/2009 12:42:57, 226304 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbhub.sys, 6.00.6002.18005 (English), 4/11/2009 12:43:16, 196096 bytes
   Driver: C:\\\\Windows\\\\system32\\\\hcrstco.dll, 6.00.6001.18000 (English), 1/21/2008 10:23:03, 15872 bytes
     Name: Intel® ICH9 Family USB Universal Host Controller - 2938
Device ID: PCI\\\\VEN_8086&DEV_2938&SUBSYS_50041458&REV_02\\\\3&13C0B0C5&2&D1
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbuhci.sys, 6.00.6001.18000 (English), 1/21/2008 10:23:03, 23552 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbport.sys, 6.00.6002.18005 (English), 4/11/2009 12:42:57, 226304 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbhub.sys, 6.00.6002.18005 (English), 4/11/2009 12:43:16, 196096 bytes
   Driver: C:\\\\Windows\\\\system32\\\\hcrstco.dll, 6.00.6001.18000 (English), 1/21/2008 10:23:03, 15872 bytes
     Name: Intel® ICH9 Family USB Universal Host Controller - 2937
Device ID: PCI\\\\VEN_8086&DEV_2937&SUBSYS_50041458&REV_02\\\\3&13C0B0C5&2&D0
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbuhci.sys, 6.00.6001.18000 (English), 1/21/2008 10:23:03, 23552 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbport.sys, 6.00.6002.18005 (English), 4/11/2009 12:42:57, 226304 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbhub.sys, 6.00.6002.18005 (English), 4/11/2009 12:43:16, 196096 bytes
   Driver: C:\\\\Windows\\\\system32\\\\hcrstco.dll, 6.00.6001.18000 (English), 1/21/2008 10:23:03, 15872 bytes
     Name: Intel® ICH9 Family USB Universal Host Controller - 2936
Device ID: PCI\\\\VEN_8086&DEV_2936&SUBSYS_50041458&REV_02\\\\3&13C0B0C5&2&EA
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbuhci.sys, 6.00.6001.18000 (English), 1/21/2008 10:23:03, 23552 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbport.sys, 6.00.6002.18005 (English), 4/11/2009 12:42:57, 226304 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbhub.sys, 6.00.6002.18005 (English), 4/11/2009 12:43:16, 196096 bytes
   Driver: C:\\\\Windows\\\\system32\\\\hcrstco.dll, 6.00.6001.18000 (English), 1/21/2008 10:23:03, 15872 bytes
     Name: Intel® ICH9 Family USB Universal Host Controller - 2935
Device ID: PCI\\\\VEN_8086&DEV_2935&SUBSYS_50041458&REV_02\\\\3&13C0B0C5&2&E9
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbuhci.sys, 6.00.6001.18000 (English), 1/21/2008 10:23:03, 23552 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbport.sys, 6.00.6002.18005 (English), 4/11/2009 12:42:57, 226304 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbhub.sys, 6.00.6002.18005 (English), 4/11/2009 12:43:16, 196096 bytes
   Driver: C:\\\\Windows\\\\system32\\\\hcrstco.dll, 6.00.6001.18000 (English), 1/21/2008 10:23:03, 15872 bytes
     Name: Intel® ICH9 Family USB Universal Host Controller - 2934
Device ID: PCI\\\\VEN_8086&DEV_2934&SUBSYS_50041458&REV_02\\\\3&13C0B0C5&2&E8
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbuhci.sys, 6.00.6001.18000 (English), 1/21/2008 10:23:03, 23552 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbport.sys, 6.00.6002.18005 (English), 4/11/2009 12:42:57, 226304 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\usbhub.sys, 6.00.6002.18005 (English), 4/11/2009 12:43:16, 196096 bytes
   Driver: C:\\\\Windows\\\\system32\\\\hcrstco.dll, 6.00.6001.18000 (English), 1/21/2008 10:23:03, 15872 bytes
     Name: Intel® ICH9 Family SMBus Controller - 2930
Device ID: PCI\\\\VEN_8086&DEV_2930&SUBSYS_50011458&REV_02\\\\3&13C0B0C5&2&FB
   Driver: n/a
     Name: Intel® ICH9 Family 2 port Serial ATA Storage Controller 2 - 2926
Device ID: PCI\\\\VEN_8086&DEV_2926&SUBSYS_B0021458&REV_02\\\\3&13C0B0C5&2&FD
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\pciide.sys, 6.00.6002.18005 (English), 4/11/2009 14:32:49, 14312 bytes
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\pciidex.sys, 6.00.6002.18005 (English), 4/11/2009 14:32:52, 43496 bytes
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\atapi.sys, 6.00.6002.18005 (English), 4/11/2009 14:32:26, 19944 bytes
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\ataport.sys, 6.00.6002.18005 (English), 4/11/2009 14:32:42, 109032 bytes
     Name: Intel® ICH9 Family 2 port Serial ATA Storage Controller 1 - 2921
Device ID: PCI\\\\VEN_8086&DEV_2921&SUBSYS_B0021458&REV_02\\\\3&13C0B0C5&2&FA
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\pciide.sys, 6.00.6002.18005 (English), 4/11/2009 14:32:49, 14312 bytes
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\pciidex.sys, 6.00.6002.18005 (English), 4/11/2009 14:32:52, 43496 bytes
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\atapi.sys, 6.00.6002.18005 (English), 4/11/2009 14:32:26, 19944 bytes
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\ataport.sys, 6.00.6002.18005 (English), 4/11/2009 14:32:42, 109032 bytes
     Name: Intel® ICH9 LPC Interface Controller - 2918
Device ID: PCI\\\\VEN_8086&DEV_2918&SUBSYS_50011458&REV_02\\\\3&13C0B0C5&2&F8
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\msisadrv.sys, 6.00.6001.18000 (English), 1/21/2008 10:23:01, 16440 bytes
     Name: Intel® 82801 PCI Bridge - 244E
Device ID: PCI\\\\VEN_8086&DEV_244E&SUBSYS_50001458&REV_92\\\\3&13C0B0C5&2&F0
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\pci.sys, 6.00.6002.18005 (English), 4/11/2009 14:32:55, 149480 bytes
     Name: Standard Dual Channel PCI IDE Controller
Device ID: PCI\\\\VEN_197B&DEV_2363&SUBSYS_B0001458&REV_02\\\\4&CACCF14&0&00E3
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\pciide.sys, 6.00.6002.18005 (English), 4/11/2009 14:32:49, 14312 bytes
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\pciidex.sys, 6.00.6002.18005 (English), 4/11/2009 14:32:52, 43496 bytes
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\atapi.sys, 6.00.6002.18005 (English), 4/11/2009 14:32:26, 19944 bytes
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\ataport.sys, 6.00.6002.18005 (English), 4/11/2009 14:32:42, 109032 bytes
     Name: Creative SB X-Fi
Device ID: PCI\\\\VEN_1102&DEV_0005&SUBSYS_00311102&REV_00\\\\4&397C2DC8&0&08F0
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\ctac32k.sys, 6.00.0001.1361 (English), 6/4/2009 02:47:06, 511000 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\ctaud2k.sys, 6.00.0001.1373 (English), 6/4/2009 02:47:14, 526232 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\ctoss2k.sys, 6.00.0001.1373 (English), 6/4/2009 02:47:34, 130072 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\ctprxy2k.sys, 6.00.0001.1373 (English), 6/4/2009 02:47:42, 14360 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\ctsfm2k.sys, 6.00.0001.1373 (English), 6/4/2009 02:47:50, 158744 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\emupia2k.sys, 6.00.0001.1373 (English), 6/4/2009 02:48:00, 95768 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\ha20x2k.sys, 6.00.0001.1373 (English), 6/4/2009 02:48:12, 1177624 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\pfmodnt.sys, 3.00.0000.0012 (English), 6/4/2009 02:48:20, 15384 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\CTEXFIFX.sys, 6.00.0001.1373 (English), 6/4/2009 02:46:56, 1324056 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\CT20XUT.sys, 6.00.0001.1373 (English), 6/4/2009 02:46:34, 171032 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\CTHWIUT.sys, 6.00.0001.1373 (English), 6/4/2009 02:46:42, 72728 bytes
   Driver: C:\\\\Windows\\\\system32\\\\ctdlang.dat, 10/7/2008 23:31:14, 321512 bytes
   Driver: C:\\\\Windows\\\\system32\\\\ctdnlstr.dat, 10/7/2008 23:31:14, 56509 bytes
   Driver: C:\\\\Windows\\\\system32\\\\CtxfiRes.dll, 6.00.0001.1373 (English), 6/4/2009 00:55:20, 2560 bytes
   Driver: C:\\\\Windows\\\\system32\\\\ctzapxx.ini, 6/4/2009 01:37:06, 54 bytes
   Driver: C:\\\\Windows\\\\system32\\\\instwdm.ini, 6/4/2009 01:37:08, 21093 bytes
   Driver: C:\\\\Windows\\\\system32\\\\CT1MGM.ROM, 2/25/2000 12:49:34, 1048576 bytes
   Driver: C:\\\\Windows\\\\system32\\\\CT2MGM.SF2, 9/22/1999 23:18:38, 2167684 bytes
   Driver: C:\\\\Windows\\\\system32\\\\default4.sfm, 1/3/2002 15:44:16, 59 bytes
   Driver: C:\\\\Windows\\\\system32\\\\default8.sfm, 1/3/2002 15:44:16, 59 bytes
   Driver: C:\\\\Windows\\\\system32\\\\default.sfm, 1/3/2002 15:44:16, 59 bytes
   Driver: C:\\\\Windows\\\\Temp\\\\ctpxst32.exe, , 0 bytes
   Driver: C:\\\\Windows\\\\Temp\\\\cttele32.dll, , 0 bytes
   Driver: C:\\\\Windows\\\\system32\\\\regplib.exe, 6/4/2009 00:36:30, 16384 bytes
   Driver: C:\\\\Windows\\\\system32\\\\a3d.dll, 80.00.0000.0003 (English), 6/4/2009 00:57:38, 60928 bytes
   Driver: C:\\\\Windows\\\\system32\\\\ac3api.dll, 6.00.0001.1373 (English), 6/4/2009 00:56:36, 48640 bytes
   Driver: C:\\\\Windows\\\\system32\\\\eaxac3.dll, 1.01.0002.0000 (English), 7/11/2001 10:51:00, 77824 bytes
   Driver: C:\\\\Windows\\\\system32\\\\ctosuser.dll, 6.00.0001.1373 (English), 6/4/2009 00:36:38, 74752 bytes
   Driver: C:\\\\Windows\\\\system32\\\\ctemupia.dll, 6.00.0001.1373 (English), 6/4/2009 00:40:12, 114688 bytes
   Driver: C:\\\\Windows\\\\system32\\\\piaproxy.dll, 6.00.0001.1373 (English), 6/4/2009 00:36:26, 68608 bytes
   Driver: C:\\\\Windows\\\\system32\\\\ctdproxy.dll, 6.00.0001.1373 (English), 6/4/2009 00:37:00, 53248 bytes
   Driver: C:\\\\Windows\\\\system32\\\\devreg.dll, 6.00.0001.1373 (English), 6/4/2009 00:31:56, 36864 bytes
   Driver: C:\\\\Windows\\\\system32\\\\ctasio.dll, 6.00.0001.1373 (English), 6/4/2009 00:37:04, 50688 bytes
   Driver: C:\\\\Windows\\\\system32\\\\ct_oal.dll, 6.00.0001.1373 (English), 6/4/2009 00:37:06, 193024 bytes
   Driver: C:\\\\Windows\\\\system32\\\\ctpxst32.exe, 1.01.0000.0059 (English), 3/13/2007 10:32:14, 89336 bytes
   Driver: C:\\\\Windows\\\\system32\\\\UDAAIM32.exe, 2.47.0000.0000 (English), 3/26/2009 16:09:18, 600217 bytes
   Driver: C:\\\\Windows\\\\system32\\\\oalinst.exe, 2.00.0006.0000 (English), 4/23/2008 06:07:50, 805400 bytes
   Driver: C:\\\\Windows\\\\system32\\\\AddCat.exe, 0.00.0000.0001 (English), 12/5/2006 14:52:40, 48400 bytes
   Driver: C:\\\\Windows\\\\system32\\\\UDAAPO32.UDA, 5/12/2009 18:34:56, 8046 bytes
   Driver: C:\\\\Windows\\\\system32\\\\CTMLFX32.UDA, 6/2/2008 11:10:04, 5458 bytes
   Driver: C:\\\\Windows\\\\system32\\\\AppSetup.exe, 1.00.0018.0005 (English), 5/18/2009 14:34:30, 22691984 bytes
   Driver: C:\\\\Windows\\\\system32\\\\CTxfiBtn.dll, 6.00.0001.1373 (English), 6/4/2009 00:55:20, 41472 bytes
   Driver: C:\\\\Windows\\\\system32\\\\CTxfiSpk.dll, 6.00.0001.1373 (English), 6/4/2009 00:55:18, 39424 bytes
   Driver: C:\\\\Windows\\\\system32\\\\Ct20xspi.dll, 6.00.0001.1373 (English), 6/4/2009 00:50:04, 15360 bytes
   Driver: C:\\\\Windows\\\\system32\\\\CTxfispi.exe, 6.00.0001.1373 (English), 6/4/2009 00:49:56, 1213440 bytes
   Driver: C:\\\\Windows\\\\system32\\\\Ctxfihlp.exe, 6.00.0001.1373 (English), 6/4/2009 00:55:16, 25600 bytes
   Driver: C:\\\\Windows\\\\system32\\\\CTxfiReg.exe, 6.00.0001.1373 (English), 6/4/2009 00:50:08, 47104 bytes
   Driver: C:\\\\Windows\\\\system32\\\\enlocstr.exe, 6/4/2009 00:33:04, 7680 bytes
   Driver: C:\\\\Windows\\\\system32\\\\killapps.exe, 1.00.0000.0001 (English), 6/4/2009 00:32:54, 12800 bytes
   Driver: C:\\\\Windows\\\\system32\\\\kill.ini, 5/27/2009 09:49:00, 285 bytes
   Driver: C:\\\\Windows\\\\system32\\\\sfman32.dll, 6.00.0001.1373 (English), 6/4/2009 00:36:36, 10240 bytes
   Driver: C:\\\\Windows\\\\system32\\\\sfms32.dll, 6.00.0001.1373 (English), 6/4/2009 00:36:34, 108544 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\cts20x.dat, 6/4/2009 00:33:10, 2091 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\ctd20x.dat, 6/4/2009 00:33:10, 26919 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\CTP0460W.DAT, 6/4/2009 00:36:00, 275836 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\CTP0466W.DAT, 6/4/2009 00:36:00, 275836 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\CTP0463W.DAT, 6/4/2009 00:36:02, 276282 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\CTP0550W.DAT, 6/4/2009 00:36:02, 276094 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\CTP0678W.DAT, 6/4/2009 00:36:08, 357983 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\CTP0679W.DAT, 6/4/2009 00:36:00, 357983 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\CTP0464W.DAT, 6/4/2009 00:36:02, 275836 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\CTP0468W.DAT, 6/4/2009 00:36:02, 275836 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\CTP0465W.DAT, 6/4/2009 00:36:02, 275836 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\CTP0469W.DAT, 6/4/2009 00:36:02, 275836 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\CTP0730W.DAT, 6/4/2009 00:36:04, 277688 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\CTP0760W.DAT, 6/4/2009 00:36:04, 275257 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\CTP046AW.DAT, 6/4/2009 00:36:04, 275508 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\CTP046BW.DAT, 6/4/2009 00:36:04, 275508 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\CTP046CW.DAT, 6/4/2009 00:36:04, 275508 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\CTP0462W.DAT, 6/4/2009 00:36:06, 275836 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\CTP055AW.DAT, 6/4/2009 00:36:04, 275766 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\CTP073AW.DAT, 6/4/2009 00:36:06, 277688 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\CTXFIGM.RFX, 7/28/2006 10:31:42, 41320 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\CTXFIEM.RFX, 7/28/2006 10:31:40, 41788 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\CTXFICM.RFX, 7/28/2006 10:31:38, 41624 bytes
   Driver: C:\\\\Windows\\\\system32\\\\data\\\\CTXFICBM.RFX, 6/23/2005 06:58:50, 7352 bytes
   Driver: C:\\\\Windows\\\\system32\\\\SBXFi.ico, 2/7/2005 17:45:22, 766 bytes
   Driver: C:\\\\Windows\\\\system32\\\\XFi.bmp, 2/7/2005 17:45:20, 3128 bytes
   Driver: C:\\\\Windows\\\\system32\\\\ctcoinst.dll, 3.00.0002.0047 (English), 6/4/2009 00:59:44, 86016 bytes
   Driver: C:\\\\Windows\\\\system32\\\\ctdvinst.dll, 0.05.0000.0047 (English), 6/4/2009 00:59:46, 181248 bytes
   Driver: C:\\\\Windows\\\\system32\\\\UDAAPO32.dll, 1.00.0008.0000 (English), 5/12/2009 12:24:44, 511488 bytes
   Driver: C:\\\\Windows\\\\system32\\\\UDAPLD32.dll, 1.00.0008.0000 (English), 5/12/2009 12:25:08, 47104 bytes
   Driver: C:\\\\Windows\\\\system32\\\\CTMLFX32.dll, 1.00.0004.0000 (English), 6/2/2008 09:40:20, 62976 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\ctdvda2k.sys, 5.13.0001.0468 (English), 6/4/2009 02:47:24, 347080 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\drmk.sys, 6.00.6001.18000 (English), 1/21/2008 10:23:20, 130048 bytes
   Driver: C:\\\\Windows\\\\system32\\\\drivers\\\\portcls.sys, 6.00.6002.18005 (English), 4/11/2009 12:42:50, 167936 bytes
   Driver: C:\\\\Windows\\\\system32\\\\WMALFXGFXDSP.dll, 11.00.6001.7000 (English), 1/21/2008 10:23:21, 1312256 bytes
   Driver: C:\\\\Windows\\\\system32\\\\SysFxUI.dll, 6.00.6001.18000 (English), 1/21/2008 10:23:21, 338944 bytes
     Name: Realtek PCIe GBE Family Controller
Device ID: PCI\\\\VEN_10EC&DEV_8168&SUBSYS_E0001458&REV_01\\\\4&2EA914C&0&00E4
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\Rtlh86.sys, 6.235.0304.2010 (English), 3/4/2010 13:50:14, 261152 bytes
   Driver: C:\\\\Windows\\\\system32\\\\RtNicProp32.dll, 1.02.0000.0003 (English), 12/3/2009 09:27:28, 80416 bytes
   Driver: C:\\\\Windows\\\\system32\\\\RTNUninst32.dll, 1.00.0000.0005 (English), 2/3/2010 12:24:36, 94208 bytes
     Name: High Definition Audio Controller
Device ID: PCI\\\\VEN_1002&DEV_AA50&SUBSYS_AA501682&REV_00\\\\4&39BD1753&0&0108
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\hdaudbus.sys, 6.00.6002.18005 (English), 4/11/2009 12:42:42, 561152 bytes
     Name: ATI Radeon HD 5800 Series
Device ID: PCI\\\\VEN_1002&DEV_6899&SUBSYS_29701682&REV_00\\\\4&39BD1753&0&0008
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\atikmdag.sys, 8.01.0001.1004 (English), 2/3/2010 12:54:34, 5313536 bytes
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\ati2erec.dll, 1.00.0000.0019 (English), 2/3/2010 11:40:18, 53248 bytes
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\atikmpag.sys, 8.14.0001.6095 (English), 2/3/2010 11:23:42, 150016 bytes
   Driver: C:\\\\Windows\\\\system32\\\\atiumdag.dll, 8.14.0010.0728 (English), 2/3/2010 11:55:34, 3653632 bytes
   Driver: C:\\\\Windows\\\\system32\\\\atiumdva.dll, 8.14.0010.0247 (English), 2/3/2010 11:37:10, 2934272 bytes
   Driver: C:\\\\Windows\\\\system32\\\\atitmmxx.dll, 6.14.0011.0022 (English), 2/3/2010 12:15:38, 159744 bytes
   Driver: C:\\\\Windows\\\\system32\\\\atiicdxx.dat, 12/5/2009 05:17:18, 198341 bytes
   Driver: C:\\\\Windows\\\\system32\\\\amdpcom32.dll, 8.14.0010.0023 (English), 2/3/2010 11:25:00, 52224 bytes
   Driver: C:\\\\Windows\\\\system32\\\\atimpc32.dll, 8.14.0010.0023 (English), 2/3/2010 11:25:00, 52224 bytes
   Driver: C:\\\\Windows\\\\system32\\\\atiadlxx.dll, 6.14.0010.1054 (English), 2/3/2010 11:24:24, 229376 bytes
   Driver: C:\\\\Windows\\\\system32\\\\atiumdva.cap, 2/3/2010 11:36:48, 491104 bytes
   Driver: C:\\\\Windows\\\\system32\\\\atimuixx.dll, 6.14.0010.1001 (English), 2/3/2010 12:14:58, 11776 bytes
   Driver: C:\\\\Windows\\\\system32\\\\atiapfxx.exe, 6.14.0010.1000 (English), 2/3/2010 12:19:14, 143360 bytes
   Driver: C:\\\\Windows\\\\system32\\\\atiapfxx.blb, 2/3/2010 12:19:16, 31240 bytes
   Driver: C:\\\\Windows\\\\system32\\\\atiesrxx.exe, 6.14.0011.1049 (English), 2/3/2010 12:16:58, 172032 bytes
   Driver: C:\\\\Windows\\\\system32\\\\atieclxx.exe, 6.14.0011.1049 (English), 2/3/2010 12:17:28, 372736 bytes
   Driver: C:\\\\Windows\\\\system32\\\\atipdlxx.dll, 6.14.0010.2562 (English), 2/3/2010 12:15:20, 356352 bytes
   Driver: C:\\\\Windows\\\\system32\\\\Oemdspif.dll, 6.15.0006.0006 (English), 2/3/2010 12:15:06, 274432 bytes
   Driver: C:\\\\Windows\\\\system32\\\\ati2edxx.dll, 6.14.0010.2514 (English), 2/3/2010 12:14:52, 43520 bytes
   Driver: C:\\\\Windows\\\\system32\\\\ATIDEMGX.dll, 2.00.3685.41938 (English), 2/3/2010 12:17:56, 446464 bytes
   Driver: C:\\\\Windows\\\\system32\\\\atioglxx.dll, 6.14.0010.9551 (English), 2/3/2010 12:01:18, 14147072 bytes
   Driver: C:\\\\Windows\\\\system32\\\\aticaldd.dll, 6.14.0010.0553 (English), 2/3/2010 11:51:18, 3649536 bytes
   Driver: C:\\\\Windows\\\\system32\\\\aticalrt.dll, 6.14.0010.0553 (English), 2/3/2010 11:52:44, 53248 bytes
   Driver: C:\\\\Windows\\\\system32\\\\aticalcl.dll, 6.14.0010.0553 (English), 2/3/2010 11:52:30, 53248 bytes
   Driver: C:\\\\Windows\\\\system32\\\\atipblag.dat, 10/27/2009 03:06:06, 1035 bytes
   Driver: C:\\\\Windows\\\\system32\\\\atiu9pag.dll, 8.14.0001.6095 (English), 2/3/2010 11:22:58, 20480 bytes
   Driver: C:\\\\Windows\\\\system32\\\\atigktxx.dll, 8.14.0001.6095 (English), 2/3/2010 11:24:04, 14848 bytes
   Driver: C:\\\\Windows\\\\system32\\\\atiglpxx.dll, 8.14.0001.6095 (English), 2/3/2010 11:24:12, 12800 bytes
   Driver: C:\\\\Windows\\\\system32\\\\atitmpxx.dll, 6.14.0011.0021 (English), 2/3/2010 11:22:36, 23040 bytes
   Driver: C:\\\\Windows\\\\system32\\\\atibtmon.exe, 2.00.0000.0000 (English), 5/12/2009 06:35:28, 118784 bytes
   Driver: C:\\\\Windows\\\\system32\\\\atidxx32.dll, 8.17.0010.0256 (English), 2/3/2010 12:12:04, 3073024 bytes
   Driver: C:\\\\Windows\\\\system32\\\\atiuxpag.dll, 8.14.0001.6095 (English), 2/3/2010 11:23:14, 27136 bytes
   Driver: C:\\\\Windows\\\\atiogl.xml, 12/8/2009 21:40:54, 20274 bytes
   Driver: C:\\\\Windows\\\\system32\\\\ATIODCLI.exe, 1.00.0000.0001 (English), 2/4/2009 05:52:02, 45056 bytes
   Driver: C:\\\\Windows\\\\system32\\\\ATIODE.exe, 1.00.0000.0001 (English), 2/19/2009 02:55:20, 294912 bytes
   Driver: C:\\\\Windows\\\\system32\\\\DRIVERS\\\\atipmdag.sys, 8.01.0001.1004 (English), 2/3/2010 12:54:34, 5313536 bytes
   Driver: C:\\\\Windows\\\\system32\\\\aticfx32.dll, 8.17.

Modifié par wolfwarp, 10 avril 2010 - 12:33 .

[joey_mork84]

Retested with no mods enabled (even disabled DLC items), only change was a naked character as almost all of my equipment is DLC or mods. Empty inventory at start, attempted stealing 10 times (nice round number, figured I would stick with that), money stolen three out of ten times with random amounts, one stealing fail (skill wasn't high enough, I suppose), and 6 stealing success with randomly generated items found for each in pack: 3 lesser health poltices, 1 quartz, 1 lesser injury kit, and one lesser lirium vial.

DA:O Patch 1.03 installed.

EDIT: Also have never recieved (never as in not since game was first purchased and installed) a Windows error message of any kind while playing other than my instant messenger randomly deciding it didn't want to run anymore once.

Modifié par joey_mork84, 10 avril 2010 - 04:39 .

[joey_mork84]

Also @Gorath: Sorry we completely derailed your thread. Hope it gets back on track soon.

[Andari_Surana]

PBM wrote...

File. Sys_treasure_h
Procedure=TS_GenerateItems
Line 488-490
// PREVENT NON-MONEY TREASURE IF CREATURE ALREADY HAS MONEY
if(GetObjectType(oTarget) == OBJECT_TYPE_CREATURE && GetCreatureMoney(oTarget) > 0)
continue;
 
This section was added to the 1.03 patch. In this case otarget is the player as determined by the call
TS_GenerateItems(oThief, nRank, nCategory, nLevel, OBJECT_TYPE_CREATURE, 1.0f, 0.0, TRUE);
From TreasureStolen.
 
This added code is in the block that determines what to do when an item is being stolen. (If it had already determined money was stolen it never got here.) Not sure why the player object would evaluate to true on the == OBJECT_TYPE_CREATURE but the behavior is consistent with the bug. IE. It will generate nothing when an Item is stolen and you have money.

Original credit to PBM.  To translate, the reason why stealing returns no items in 1.03 the line including " == OBJECT_TYPE_CREATURE " always evaluates as true, causing the next line to trigger which is to skip out of the function.  Re looking at this function and PBM's analysis i may disagree w/ PBM as to the cause, as it appears the only way for this line to always be true is if "GetCreaturemoney >0" is erroneously always evaluating true....  In other words, the bug is that DA always thinks creatures has money when it gets to this node.

I think PBM was saying it was because comparing object types between player and creature was improperly returning true - but i think he may have made a mistake in thinking "otarget" was somhow associated with the thief  (as in target thief making the skill check, instead of target creature) - but he was looking at more of the code than this snippet - and i can't see what value was passed to otarget from just this code).    object type(otarget) == creature, should almost always evalutate true (unless flagged as say a PC or special character), so i can't imagine the bug being on the left hand side of  "&&" sign.

But in either case, removing this line is the cause of the steal fix in mods.
And this was the line that changed that broke stealing in 1.03....

As to why it works on  your computer joey....i'm a bit incredulous.

Bottom line, if stealing works on your version, then it must  be that your version of DA is using a script in 1.03 that is different from basically everyone elses.  At any rate, its not going to be a difference based on the type of computer you have, memory, or any other hardware.  Whatever the cause, its  not going to be a system (hardware/operating system) dependent difference, but a difference in installation of things that may have modified this script (mods, DLC, or something....)

Modifié par Andari_Surana, 11 avril 2010 - 05:59 .

[joey_mork84]

We've already found the possible cause, Andari. Only possible cause would have been that the code involving the Steal function bug got corrupted during download when I got the patch. It works the same with all mods and DLC disabled (as I said above). No need to be skeptical. It can happen as codes are not 100% consistant 100% of the time. I just happen to be lucky enough to have it happen to me

*Sigh*..

Whether you wish to believe it or not, Andari, Stealing works perfectly fine for me, with or without DLC and mods enabled (as I've said numerous times). Now, I believe we can move on, unless you would like to keep going with this even though this issue has been resolved and there is no need.

Modifié par joey_mork84, 11 avril 2010 - 04:44 .

[Tyrax Lightning]

Hot tip: When reporting what Motherboard you're using, beware that some have more than one 'Revision'. For example, the one i've put into my new puder build, the GIGABYTE GA-MA770T-UD3P AM3 AMD 770 ATX AMD Motherboard, has a 'Revision 1.0' version & a 'Revision 1.1' version. I've checked mine for future reference & it's the Revision 1.1 version. This matters because different revision Motherboards sometimes have different Driver needs, Drivers for one revision might not work right on other revisions of the same Motherboard family.

This is fearsomely easy to not know about, forget about, &/or overlook.

Hope I helped.

Modifié par Tyrax Lightning, 11 avril 2010 - 05:19 .

[joey_mork84]

I've heard of people having that problem, Tyrax. A friend of mine had a hard time getting the right drivers for his new motherboard and that seems to be his issue although, I'm not completely sure. I haven't been hands on with his pc enough to know if that is the cause or not, but it does seem to fit his problem.



His motherboard is very particular to what you put on it, as well. I blame faulty manufacturing, but it could be anything. There are certain brands of parts it simply won't use. It's very picky in that respect. For example, we ordered RAM for it three seperate times, all Kingston brand, and it refused to detect them. We eventually got it to work with Corsair and it hasn't had a problem since then. I still say he needs another motherboard, but he won't listen lol.



Thanks for getting the thread back on track, btw.

[Marafice Eye]

My issues have nothing to do with the steal function. But I can tell you with 100% certainty that 1.03 broke my game. I get random CTDs to the point that I am saving every 2-3 minutes in case of a crash. When it does crash, my last save game won't load, if I try, it crashes yet again. I load a previous save and it's full of graphical glitches. Blood stains on the ground are big flickering red squares, armor pops in and out on characters, spell effects show up as squares, ruining the look of the characters.



Before 1.03, none of this happened. It was stable, never CTD'd, ran as smooth as I could get it on my system.



So with that knowledge, you tell me that 1.03 is fine and nothing's wrong with it. My game is so broken I'm about to reinstall and stick with 1.02a.

[Tyrax Lightning]

joey_mork84 wrote...

I've heard of people having that problem, Tyrax. A friend of mine had a hard time getting the right drivers for his new motherboard and that seems to be his issue although, I'm not completely sure. I haven't been hands on with his pc enough to know if that is the cause or not, but it does seem to fit his problem.

His motherboard is very particular to what you put on it, as well. I blame faulty manufacturing, but it could be anything. There are certain brands of parts it simply won't use. It's very picky in that respect. For example, we ordered RAM for it three seperate times, all Kingston brand, and it refused to detect them. We eventually got it to work with Corsair and it hasn't had a problem since then. I still say he needs another motherboard, but he won't listen lol.

Thanks for getting the thread back on track, btw.

No problem!

I admit, I dunno how relevant Motherboard Revision is, but I still can't help but to think it's still better safe than sorry to try to match Motherboard Revision to Drivers. Ya never know if there may indeed be something different between revisions, after all, there must be a reason why a new revision of Motherboard was made, I would think.

For the RAM compatibility issue, it should be possible to Google your Manufacturer's Home Site. Then you should be able to find the exact model & revision of Motherboard, & it should have a RAM Compatibility List. You wanna use RAM from that list, then if it goes wrong, ya can at least hold the Manufacturer responsible, or RMA the RAM, one of the 2. If ya pick RAM without such a list, you're gambling on success chance.

Lastly, I agree that people with problems need to list as much important info as possible, or we may never find the faults to fix them. Exact OS, tech specs, mods used or not used, symptoms, & even which installation method of DA:O ya used. (As in, Steam, Retail, etc.)

[joey_mork84]

Marafice Eye wrote...

My issues have nothing to do with the steal function. But I can tell you with 100% certainty that 1.03 broke my game. I get random CTDs to the point that I am saving every 2-3 minutes in case of a crash. When it does crash, my last save game won't load, if I try, it crashes yet again. I load a previous save and it's full of graphical glitches. Blood stains on the ground are big flickering red squares, armor pops in and out on characters, spell effects show up as squares, ruining the look of the characters.

Before 1.03, none of this happened. It was stable, never CTD'd, ran as smooth as I could get it on my system.

So with that knowledge, you tell me that 1.03 is fine and nothing's wrong with it. My game is so broken I'm about to reinstall and stick with 1.02a.

I don't think anyone said the patch was 'fine'. I was just saying that when reporting problems, people need to remember to use the form given by the moderators. System specifics need to be known in order to better solve the problems.

As far as the patch being 'fine', I said that it works for me and my system with great results. Very few bugs, if any, and none of them are game breaking or game crashing. Find the 1.03 bug reporting thread, give a description of your problems followed by a detailed list of your system specs including game version and retailer (store, Steam, ect..). There may very well be easy fixes for all of your problems, but you have to remember to follow the bug reporting proceedure.. Hope that helps.

[jlc_38]

wolfwarp wrote...

joey_mork84 wrote...

I, personally, am just so tired of hearing people saying "Patch 1.03 for DA:O sucks! Don't get it, its full of problems!".. It obviously varies from system to system and person to person since everyone is having different problems. I have not had a single problem with the game since getting patch 1.03, so therefore, saying "The patch is broken and full of bugs" is entirely inaccurate.

Now that I'm done ranting for the moment.. What Gorath has said is right, you need to remember to list your system specs with the fill-in-the-blank form above, along with listing all mods you have installed as some of them can cause issues with the new patch.

Seriously, are you reading the forum on these pain that people are suffering or not?  I personally have posted a number of Windows error reports onto this forum.  No news from the developers.  Sure, give us a format, even better, a tool and we are happy to copy and paste the error messages onto this forum.  I still have tons of errors on my Windows event log.  But I am just so tired of posting errors and see no results.

Or better yet give us a refund for both DA:O and Awakening
because you are the ones the broke the game in the first place. And for the
guys that are acting all high and mighty about how we should post our problems,
go read the 40 pages from PC gamers that have spent their hard earned dollars
on a game, only to have it broken by the guys that made it! Or how about all
the PC gamers that have spent 70+ hours playing the game, are almost done, then
have installed the 1.03 patch and found that there game is now crashing every
5-10 min.?

This is pathetic. I hope that no one buys this load of BS that is now being
propagated. Victor sounds like a damn politician with all of his double speak.

 

Why not come clean and just admit you really don’t give a
damn about the PC market anymore, and that we are out of luck. I’ve seen game
companies that only have a handful of programmers do a better job then your
mammoth company is doing.

It would be one thing if this was a 10 hours FPS, but this
is a 70+ hours game that can be replayed a hundred different ways, and the expansion
adds even more. This is why we are so upset. RPG’s are supposed to be playable.
People invest a lot of their time, and expect that the company that made the
game will not mess up the code, just so they can sell more product.

Modifié par jlc_38, 12 avril 2010 - 06:52 .

[joey_mork84]

And for the guys that are acting all high and mighty about how we should post our problems,
go read the 40 pages from PC gamers that have spent their hard earned dollars
on a game, only to have it broken by the guys that made it!

Who is acting 'all high and mighty'? Nobody. We are simply telling you that the best way to have it fixed is to report the bugs with the form provided. If you don't wish to do this, you don't wish to have the game fixed, so therefore should not complain.

Or how about all the PC gamers that have spent 70+ hours playing the game, are almost done, then
have installed the 1.03 patch and found that there game is now crashing every 5-10 min.?

Quick fix: Roll back to 1.02.

Long fix: Wait for next patch.

This is pathetic. I hope that no one buys this load of BS that is now being
propagated. Victor sounds like a damn politician with all of his double speak.

Victor as a double speaking politician? Sounds like a plan to me

Why not come clean and just admit you really don’t give a damn about the PC market anymore, and that we are out of luck. I’ve seen game companies that only have a handful of programmers do a better job then your
mammoth company is doing.

Doesn't give a damn about PC market? Tell that to the PS3/Xbox owners that had to wait what seemed like an eternity for RtO.

It would be one thing if this was a 10 hours FPS, but this
is a 70+ hours game that can be replayed a hundred different ways, and the expansion
adds even more. This is why we are so upset. RPG’s are supposed to be playable.
People invest a lot of their time, and expect that the company that made the
game will not mess up the code, just so they can sell more product.

So you're saying they intentionally messed up the game's code in order to 'sell more product'.. Did you even think about that before you let your fingers do the walking? How are they selling more product by doing this? Did someone talk you into PAYING FOR the patches? If so, I can see why you would post nonsense like your entire reply.

[Tyrax Lightning]

jlc_38 wrote...
And for the guys that are acting all high and mighty about how we should post our problems, go read the 40 pages from PC gamers that have spent their hard earned dollars on a game, only to have it broken by the guys that made it!

I try to be of help, & that's 'high & mighty'? ... 

With all due respect, BioWare needs info & aid at finding the bugs to be squashed. Those 40 pages of PC Gamers need to aid us with info too. Telling BioWare to 'automatically succeed at fixing the bugs, YESTERDAY!!!' does noone any good. That's like throwing them into a huge castle with only flyswatters for equipment & telling them to hunt that castle for a handful of beetles in 1 day or they can kiss their jobs goodbye. Do you wanna try that? Computer code is terrifyingly massive. There might be more code in DA:O then the number of characters/digits currently typed out on all these Topics in all these Forums.

Speaking of Computer Code, I can't help but to wonder if it's getting too bulky & unwieldy again. Anyone agree, or disagree?

[joey_mork84]

Love the poll, Tyrax! Great to see how everyone feels on that subject. I, myself, think its fine as it is for now, but could definitely have something done about it in the future..

EDIT: Fixed spelling errors.

Modifié par joey_mork84, 12 avril 2010 - 05:51 .

[Gorath Alpha]

nosecone2010 wrote...

Perhaps the data in Dragon Age\\\\\\\\systeminformation.xml would be suitable? Along with reporting which version of DA:O is being used, of course.

IMO, the totally unnecessary HTML / XMLcode  included is extremely non-beneficial, and renders that option a very poor one, similar to asking for an entire DxDiag report!   If anyone cannot use Windows' own built-in functions to collect what is needed, there are beaucoup utilities, such as Evergreen Home, that will do it for them very easily. 

(Edited: I couldn't turn up a current download for the successor to AIDA32, it seems that only the commercial version is still readily available, so maybe I must start suggesting "SIW" from now on.

www.techsupportalert.com/best-free-system-information-utility.htm  )

Gorath
-

Modifié par Gorath Alpha, 13 avril 2010 - 12:04 .

[Tyrax Lightning]

joey_mork84 wrote...

Love the poll, Tyrax! Great to see how everyone feels on that subject. I, myself, think its fine as it is for now, but could definitely have something done about it in the future..

EDIT: Fixed spelling errors.

Many thanks! I personally think our current code's gotten awfully bulky & unwieldy, but then again, i'm a puder padawan, so that sheer size of code can still look intimidating.

I worry that many don't realize how HUGE programs are in total bits/bytes. They're asking the BioWare Devs to find a handful of bugs in a program that could probably be translated to Hay for the 'needle in a haystack analogy'. If each bit of code was 1 strand of Hay, & each bug was a needle, then think a couple of palmfuls of needles in a haystack that could completely take up an entire football field. & programs that wanna look worth buying have nowhere to go but bigger & more intense in size. All of ya, raise your hand if ya wanna be asked to find a handful of needles in a football size haystack in only a couple of weeks or else...

We need targetting aid to get those bugs squashed, or DA:O isn't gonna get any better.