| Author |
Message |
| Registered: October 18, 2007 | | Posts: 32 |
| | Posted: | | | | Quoting Telecine: Quote:
I suspect that your problem is one of application compatibility with the Homeseer suite of products. You may be able to obtain some assistance from that forum.
I think that all you can try is to unistalll Homeseer and reinstall DVD Profiler. If DVD Profiler runs fine, try adding back the Homeer product set one at a time until you find the offending components/s that stop DVD Profiler from working. I think I mentioned this already, but I haven't even installed Homeseer yet. |
|
| Registered: March 14, 2007 | Reputation:  |  Posts: 820 |
| | Posted: | | | | Try running your Homeseer products as a Service. I suspect that there will be fewer compatibility issues if you do that. Instructions here. | | | | Last edited: by Telecine |
|
| Registered: March 14, 2007 | | Reputation: | | Posts: 820 |
| | Posted: | | | | Quoting zymurgist: Quote:
Quoting Telecine:
Quote:
I suspect that your problem is one of application compatibility with the Homeseer suite of products. You may be able to obtain some assistance from that forum.
I think that all you can try is to unistalll Homeseer and reinstall DVD Profiler. If DVD Profiler runs fine, try adding back the Homeer product set one at a time until you find the offending components/s that stop DVD Profiler from working.
I think I mentioned this already, but I haven't even installed Homeseer yet. Ok then. What non-standard hardware do you have installed? Can you go to Event Viewer in Control Panel > Administrative Tools > Event Viewer > Application and System. Sort by Errors and see if there are any Error Events that relate to attempting to run the DVD Profiler application. If you find anything of interest, post the results please. | | | | Last edited: by Telecine |
|
| Registered: March 31, 2007 |  Posts: 13 |
| | Posted: | | | | see my new topic. | | | | Last edited: by Roberto67 |
|
| Registered: March 14, 2007 | | Posts: 3,830 |
| | Posted: | | | | Quoting zymurgist: Quote:
The only file missing is Databases.dod, but I assume that 's because its crashing before it can create the database.
Already rebuilt the host. Same problems. XP Home is next. Databases.dod that is in the zip file will be useless, it has to be created on a machine with the same file structure. C: \Documents and Settings\ \ XXXXXX\ where XXXXXX is the name of the directory of your Administrator or Username \Application Data\ \DVD Profiler\ If you have another machine running with the same structure then you could create this file and transfer it to rack computer | | | | Sources for one or more of the changes and/or additions were not submitted. Please include the sources for your changes in the contribution notes, especially for cast and crew additions. |
|
| Registered: October 18, 2007 | | Posts: 32 |
| | Posted: | | | | Quoting Telecine: Quote:
Ok then.
What non-standard hardware do you have installed?
Can you go to Event Viewer in Control Panel > Administrative Tools > Event Viewer > Application and System. Sort by Errors and see if there are any Error Events that relate to attempting to run the DVD Profiler application.
If you find anything of interest, post the results please. No hardware at all other than motherboard. It has a built in NIC and graphics. Event viewer: Quote:
Hanging application dvdpro.exe, version 3.1.1.1171, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
Faulting application dvdpro.exe, version 3.1.1.1171, faulting module dvdpro.exe, version 3.1.1.1171, fault address 0x000da77a. |
|
| Registered: March 14, 2007 | | Posts: 3,830 |
| | Posted: | | | | this also with 1 GB of memory?
Can you try this? go to c:\program files\dvd profiler\
right click on dvdpro.exe select properties choose tab compatibility and mark the compatibility modus and select windows 2000 modus if that did not work go gradualy down in modus.
it runs in:
windows 2000 modus not so nice view windows NT 4.0 (service pack 5)don't go any lower then windows NT 4.0 (service pack 5) the dvd profiler hangs. | | | | Sources for one or more of the changes and/or additions were not submitted. Please include the sources for your changes in the contribution notes, especially for cast and crew additions. | | | | Last edited: by ? |
|
| Registered: March 14, 2007 | | Posts: 3,830 |
| | Posted: | | | | Quoting zymurgist: Quote:
Hanging application dvdpro.exe, version 3.1.1.1171, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
Faulting application dvdpro.exe, version 3.1.1.1171, faulting module dvdpro.exe, version 3.1.1.1171, fault address 0x000da77a. before the event where you're asked to send a report to microsoft, not any other fault messages? | | | | Sources for one or more of the changes and/or additions were not submitted. Please include the sources for your changes in the contribution notes, especially for cast and crew additions. |
|
| Registered: March 14, 2007 |  Posts: 1,777 |
| | Posted: | | | | Personally, I'm starting to wonder if there isn't some sort of hardware fault, something like upper memory. Bios configurations for memory can be an issue as well if they are too aggressive. | | | | Last edited: by mdnitoil |
|
| Registered: December 18, 2007 | | Posts: 3 |
| | Posted: | | | | I think we need some remote debugging on the machine in question to track down that problem. If you are willing to, zymurgist, I could walk you through this via VNC remote control (there is a one-click solution that requires no software installation at all to work) and WinDbg as JIT debugger to capture a minidump of the crash. With the information from the minidump, it should be possible to track down the problem and probably send a detailed problem description to "Mr. Invelos"  | | | | Last edited: by systeddy |
|
| Registered: October 18, 2007 | | Posts: 32 |
| | Posted: | | | | Quoting Giga Wizard: Quote:
this also with 1 GB of memory?
Can you try this? go to c:\program files\dvd profiler\
right click on dvdpro.exe select properties choose tab compatibility and mark the compatibility modus and select windows 2000 modus if that did not work go gradualy down in modus.
it runs in:
windows 2000 modus not so nice view windows NT 4.0 (service pack 5)don't go any lower then windows NT 4.0 (service pack 5) the dvd profiler hangs. I don't have 1G of memory to throw in there and I'm not going to buy any unless I know that its definitely the issue. Tried changing compatibility modes, but still crashing. BTW, I installed Win XP Home and its still crashing. |
|
| Registered: October 18, 2007 | | Posts: 32 |
| | Posted: | | | | Quoting Giga Wizard: Quote:
Quoting zymurgist: Quote:
Hanging application dvdpro.exe, version 3.1.1.1171, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
Faulting application dvdpro.exe, version 3.1.1.1171, faulting module dvdpro.exe, version 3.1.1.1171, fault address 0x000da77a.
before the event where you're asked to send a report to microsoft, not any other fault messages? No other fault messages. |
|
| Registered: October 18, 2007 | | Posts: 32 |
| | Posted: | | | | Quoting mdnitoil: Quote:
Personally, I'm starting to wonder if there isn't some sort of hardware fault, something like upper memory. Bios configurations for memory can be an issue as well if they are too aggressive. I have not made any Bios changes. Is there something I can do to test your theory? |
|
| Registered: March 14, 2007 | | Posts: 1,777 |
| | Posted: | | | | One thing we used to do was bounce memory chips around. Depending on how many pieces are installed on your motherboard, possibly removing a piece and shuffling things around to see if you can isolate a bad piece. Of course, if you only have a single stick of memory this is a dead end. Beyond that, you can always go to some of those free web diagnostic sites and run the memory test. I think they're the standard sequential and then random tests, but each bit will get hit. |
|
| Registered: May 8, 2007 | | Posts: 824 |
| | Posted: | | | | I suspect there is an incompatibility with his graphics drivers and DVD Profiler.
zymurgist, are you ABSOLUTELY CERTAIN you get the SAME CRASH information when you try to run DVD Profiler in safe mode? ("DVD Profiler has encountered a problem and needs to close. We are sorry for the inconvenience.")
Again, hit F8 repeatedly as your computer boots, and you should get a menu. You did get that menu, right? Select "Safe Mode".
After Windows XP boots in Safe Mode, try running DVD Profiler.
What happens exactly? | | | | 99.9% of all cat plans consist only of "Step 1." | | | | Last edited: by Grendell |
|
| Registered: December 18, 2007 | | Posts: 3 |
| | Posted: | | | | zymurgist, try installing WinDbg as a JIT debugger, this will allow you to collect some more information about that odd crash. Download WinDbg from MS ( Debugging Tools Download from MS) and install it. After successful installation open a command lin prompt: Click on Start, Run..., enter "cmd" (without the quotes) and hit enter. A new window with black background should appear. change the current path to C:\Programs\Debugging Tools for Windows\ (or whereever you chose to install it) by entering "cd "c:\Programs\Debugging Tools for Windows"". Please note the extra quotation marks enclosing the path, this is just to make sure that the cd command finds the correct path (there are spaces in the path which can be problematic sometimes). type "dir windbg.exe" to check if you have the correct folder, it should list one item found. now enter "windbg -I" (that is windbg followed by a space, a minus and a capital i) and you should get a success or fail message. If it fails we need to investigate further what's going on, but I assume you'll get a success message. From this point on, any unhandled exceptions (such like your DP crash) will be redirected to WinDbg first to allow debugging of the problem. WinDbg isn't exactly user-friendly in usage, but we'll only need a little bit of it. Close the command prompt by typing "exit" and hitting enter. Now fire up DP. You should see the usual stuff happening, yet this time WinDbg should open up and prompt you for your instructions. Near the bottom of the window, there is a command line with a flashing cursor. Enter ".lastevent" (no caps, no spaces and a leading point!), then copy and paste the output here if possible. |
|