Windbg Unable to find module 'Wdf01000.sys' - driver

I have Windbg running and want to check source level debugging of WDF.
If I run the command "!lmi wdf01000.sys", I get the following result:
kd> !lmi Wdf01000.sys
Loaded Module Info: [wdf01000.sys]
wdf01000.sys not found
If I look in the symbol cache the wdf01000.pdb is there. I use the latest Windows 10 version with the actual WDK.
I followed the article new support for source-level debugging of WDF in Windows 10

I found it myself. I forgot to call .reload.
Then I came into the next problem and this was that the source was not shown. For this read in addition to the above article this.
[l+, l- (Set Source Options)][1]
Yes, the first is the worst. :-)

Related

Delphi Can't load package the specified module cannot be found

Delphi 10.3
Windows 10
I am trying to install the TDataSet component for Advantage Database. I have already installed it to my laptop without any trouble. The laptop has the same systems.
On my desktop I get the error Can't load package... the specified module cannot be found.
I have searched for answers for hours. Others with the same problem have solved it with path adjustments. The modules do exist and are on the search path. I even added it to the system environment variable. That was not necessary on the laptop. There is only one .dcp package that is not a regular system file and it compiles to the standard Public\Embarcadero...\dcp directory.
After hours of searching I'm ready to give up. Any new ideas?
The required section contains:
adsd103Rio.dcp, //I triple checked the spelling
dcldb.dcp,
designide.dcp,
rtl.dcp,
vcl.dcp
Any new ideas?
Gary
i had same issue. spent hours on this.
Here is the solution that worked for me:
go to this thread:
Can't load package %s error while installing a package
Look for answer that starts with this:
Run Process Monitor from http://SysInternals.com and set the filters to intercept only file operations ( toolbar rightmost buttons ) of your Delphi IDE process (check the process name in TaskManager or shortcut properties (it is bds.exe for Delphi XE2), then add the filter similar to Include / Process Name / Ends With / bds.exe ).
Run as a administrator, it works for me.
copy all your components in below path:
C:\Users\Public\Documents\Embarcadero\Studio\20.0\Bpl
This advise has really solved problem on my side!
I had same issue. please copy all your components in below path:
C:\Users\Public\Documents\Embarcadero\Studio\20.0\Bpl

driver is not loading in wince 6.0 issue

I added my driver in wince 6.0 platform builder. It compiles sucessfully and added in nk.bin(i checked manully by open nk.bin in vs2005) also reg file contaning that driver enrty. I did below processure to add my driver.
Copy driver code into “$(_TARGETPLATROOT)\Files\MyDriver”
Add below line at “platform.bib”
MyDriver.dll $(_TARGETPLATROOT)\Files\MyDriver\MyDriver.dll NK SHK
Add below line at “platform.reg”
#include "$(_TARGETPLATROOT)\Files\MyDriver\MyDriver.reg"
But when I flash that, nk.bin. driver is not loaded on board. I checked with tool which help to check which driver loaded on board.
Does anyone have idea about that?
We have no idea what is in mydriver.reg, so if there's a problem there, or the resulting platform.reg, then that could be an issue.
There are a few ways to diagnose this problem. The first step would be to check ce.bib and platform.reg and make sure the expected entries are there. If the driver or it's registry entries are not ending up in the OS, that would cause a problem.
If that looks good, then there are two steps you can take.
Build a Debug version of the OS, copy the debug version of device.exe into the FLATRELEASEDIR of a Release build and call makeimg. This will give you a release build with a debug version of device.exe. Boot up and look at the debug messages for when it attempts to load the driver and look at the report of the failure.
Create a simple application that calls ActivateDevice and look at the return value from it. Outputting debug messages from the driver in DllMain and XXX_Init is usually helpful as well.

not enough space for environment appears when executing ".exe" file

I am trying to use an application called CLUT.exe which is an old application for MS-DOS that can be used to reindex NTX files for DBF databases.
(This is not the main topic, but I am just writing this if someone wants to test the app and don't trust at all about the content).
The problem starts when trying to run the command line version through console (cmd.exe) and this error appears:
C:\>CLUT.exe [arg1] [arg2] [arg3]
run-time error R6009
- not enough space for environment
So, according to what I've searched, this could be a possible solution:
http://support.microsoft.com/default.aspx?scid=kb;en-us;230205
but it doesn't work and every alternative that I found to solve this over the internet is the same.
Another alternative could be to make right-click in the .exe file, go to Properties then Memory tab and increase the Initial environment memory from Auto to the max value but it doesn't work too.
Well, I am stuck and no "possible" solution is working for me. If someone is interested, knows more about this issue and want to test, you can download the application from here (click "Free Download" green button):
http://www.filebasket.com/free/Development-Clipper-programming-language/clut-exe/13996.html
or directly from my DropBox:
https://dl.dropbox.com/u/15208254/stackoverflow/clut_214.rar
Just to know, I am using Windows 7 and the CLUT.exe application is a Clipper based app (old programming language) that may run under windows console (cmd.exe).
Wikipedia does mention other dos emulators but, oddly, doesn't mention BOCHS.
Reindexing NTX files is not a difficult thing to do, and can be done with tools other than CLUT. For example, many of the utilities listed on this part of Download32 could be used. Otherwise, you could write your own using Harbour Project or xHarbour. Or contact me off list and I'll cook up something in Clipper 5.3.
LATER
If I read the README correctly for CLUT, it's a replacement for the DBU utility that comes with Clipper 5.x. I can supply you with a build of that if you're unsuccessful with other approaches.

Error in xml file while creating a project in black berry

I just created a new project in the eclipse and as soon as it was created, it is created with the error below
InvalidRegex:
Pattern value '([a-zA-Z_]{1,63}[\s-a-zA-Z_0-9.]{0,63}[;]?)*' is not a valid
regular expression.
The reported error was: ''-' is an invalid character range.
Write '\-'.' at column '{2}'.
BlackBerry_App_Descriptor.xml Unknown XML Problem.
This is the problem which we will get when there is jre7 in our system which is not supported by eclipse
What is the problem here? How can i rectify this? thank you
Google shows this is related to Java 7. Check these two links:
http://supportforums.blackberry.com/t5/Java-Development/problem-with-the-BlackBerry-App-Descriptor-xml-in-Eclipse-Plug/td-p/959029 and http://cdrussell.blogspot.com/2011/09/blackberry-eclipse-error-invalid-regex.html
The second one tells:
Turns out this could be caused by having Java JRE 7 installed on your
machine. The BlackBerry plugin doesn't support this yet, Eclipse might
be trying to use that.
The fix? You simply have to edit the eclipse.ini that will live in the
same directory as your eclipse.exe that you use to start the IDE.
Closing Eclipse and making a backup of eclipse.ini before you do this
would be a good idea.
Find the line "openFile" and immediately after, add the following:
-vm C:/Program Files/Java/jre6/bin/javaw.exe [or wherever your jre6 directory might be]
Cross your fingers and restart Eclipse. Rebuild your projects.

Updating UMDF drivers during development

I am having some trouble updating UMDF drivers using "devcon" during a
standard code-deploy-debug cycle. The problem is that "devcon update" isn't
really updating anything unless the version number or the date of the DLL
file and the INF file has changed from what is stored in the system's driver
cache folder. After a maddening series of experiments I've discovered that
one way to force the thing to use the latest files is by doing the
following:
Change the parameters passed to
"stampinf.exe" in "makefile.inc" by
explicitly setting a version with
the "-v" option.
Modify the
resource script file ("DRIVER_NAME.rc") to first define
VER_USE_OTHER_MAJOR_MINOR_VER
before including "ntverp.h" and then
explicitly define
VER_PRODUCTMAJORVERSION and
VER_PRODUCTMINORVERSION. You'll
note that this system does not allow
us to change the build and the
revision numbers. On Win7 this
seems to be fixed at 7600 and 16385
in "ntverp.h". Is this by design?
So, I first modify "makefile.inc" and set the "-v" option to something like
"1.1.7600.16385" manually incrementing the minor version for every single
build and then modify the RC file and update VER_PRODUCTMINORVERSION with
the same number.
Alternatively, if I run a command prompt under the SYSTEM account and go and
delete the driver cache folder in
"C:\windows\system32\DriverStore\FileRepository\DRIVER FOLDER" before
running "devcon" then that works too.
Now, I am thinking I am missing something fairly basic here as this seems to
be a rather painful way of doing it. Please help! Thanks!
Why can't you just unplug the device and replace the unloaded DLL? You shouldn't need to reinstall the driver, just replace the module. Note that you shouldn't do this during production or anything that has to do with customers, but if you're writing a driver, just slam in the new module with the same version number.
On Win7 this seems to be fixed at 7600 and 16385 in "ntverp.h". Is this by design?
Yep, at least until the next service pack
As Paul Betts has suggested above, the way to go seems to be to simply replace the UMDF DLL directly in the driver folder (for e.g. c:\windows\system32\drivers\umdf\) after disabling the device either in the device manager or using "devcon". I'd asked this question on Microsoft's device drivers newsgroup before posting here but hadn't got a satisfactory response - but some folks ended up responding there after I posted here! So I'll put up a link to that post as well:
http://bit.ly/6PDxKT

Resources