Drvstore Folder Vista

Vista How to Restore Folder Icons to Default. Did you notice any problem or somewhat different in the folders? Recently, I installed a program to customize the current Windows Vista theme and icons. I am so amazed with the program because they gave three themes for free! But one thing I got so angry.

Comments

• Well, first of all, there IS no signature enforcement in 32-bit Windows.. so that's not your problem.
  Also, it looks to ME like your INF worked according to the log:
  <<< [Exit status: SUCCESS]
  It looks like your catalog file name is MISSING (note the name in the log is ')?
  Just remove the catalog file line from the INF.
  Did you run your INF through ChkInf?
  Peter
  OSR

  0·Share on Facebook
• I keep seeing posts that state there is no signing requirements for 32 bit
  Windows. If you use PsSetCreateProcessNotifyRoutineEx the driver must be
  signed, even for a 32 bit driver.
  Search for the /INTEGRITYCHECK linker option. This option is required if you
  use this function.
  Bill Wandel
  -----Original Message-----
  From: [email protected]
  [mailto:[email protected]] On Behalf Of [email protected]
  Sent: Friday, April 29, 2011 9:19 AM
  To: Windows System Software Devs Interest List
  Subject: RE:[ntdev] Windows Vista 32 Problem with Inf File
  Well, first of all, there IS no signature enforcement in 32-bit Windows..
  so that's not your problem.
  Also, it looks to ME like your INF worked according to the log:
  <<< [Exit status: SUCCESS]
  It looks like your catalog file name is MISSING (note the name in the log is
  ')?
  Just remove the catalog file line from the INF.
  Did you run your INF through ChkInf?
  Peter
  OSR
  ---
  NTDEV is sponsored by OSR
  For our schedule of WDF, WDM, debugging and other seminars visit:
  http://www.osr.com/seminars
  To unsubscribe, visit the List Server section of OSR Online at
  http://www.osronline.com/page.cfm?name=ListServer
• If i remove the catalog line the chkinf shows these:
  Line 6: (E22.1.1081) Directive: CatalogFile required (and must not be blank) in section [Version] for WHQL digital signature.
  And if i add the line there is no error neither warnings in the chkinf, but in both cases the installation fails.
  As i said i can run the inf in the windows XP and 7-32 bits with no problem, the only one that gives me problem is windows Vista 32 bits, that is why i ask if there is something special i have to add in the inf file to the windows Vista 32 bits.
  Thanks
• On 04/29/2011 06:12 PM, [email protected] wrote:
  > And if i add the line there is no error neither warnings in the chkinf, but in both cases the installation fails.
  chkinf itself does not test/check the CAT file.
  If a CAT file is referenced in the INF file, the _installer_ checks if
  the CAT file it is present and matches your binaries.
  You have to create a CAT file with inf2cat, then sign it with
  signtool.exe. There are walkthroughs on MSDN about how to do this.
• Thanks, i checked the inf2cat program and it gives me the next warnings:
  22.9.8 Possible Windows XP/Windows Server 2003 file redistribution violation (32usbser.sys --> usbser.sys). File not copied by installation inf so this is a warning only
  22.9.8 Possible Windows Vista/Windows Server 2008 file redistribution violation (32usbser.sys --> usbser.sys). File not copied by installation inf so this is a warning only
  22.9.8 Possible Windows XP/Windows Server 2003 file redistribution violation (32usbser.sys --> usbser.sys). File not copied by installation inf so this is a warning only
  22.9.8 Possible Windows Vista/Windows Server 2008 file redistribution violation (32usbser.sys --> usbser.sys). File not copied by installation inf so this is a warning only.
  So that means that i have to include the usbser.sys in my current INF file??
• [email protected] wrote:
  > Thanks, i checked the inf2cat program and it gives me the next warnings:
  >
  > 22.9.8 Possible Windows XP/Windows Server 2003 file redistribution violation (32usbser.sys --> usbser.sys). File not copied by installation inf so this is a warning only
  >
  > 22.9.8 Possible Windows Vista/Windows Server 2008 file redistribution violation (32usbser.sys --> usbser.sys). File not copied by installation inf so this is a warning only
  >
  > 22.9.8 Possible Windows XP/Windows Server 2003 file redistribution violation (32usbser.sys --> usbser.sys). File not copied by installation inf so this is a warning only
  >
  > 22.9.8 Possible Windows Vista/Windows Server 2008 file redistribution violation (32usbser.sys --> usbser.sys). File not copied by installation inf so this is a warning only.
  >
  > So that means that i have to include the usbser.sys in my current INF file??
  No, it certainly does not. Are you aware of the difference between an
  error and a warning?
  --
  Tim Roberts, [email protected]
  Providenza & Boekelheide, Inc.

  Tim Roberts, [email protected]
  Providenza & Boekelheide, Inc.

• >No, it certainly does not. Are you aware of the difference between an
  >error and a warning?
  Yes, but i want to discard any possible warning or error to find the way to install the driver on Windows Vista 32, because i do not find a reason why the same inf files section and .sys files works right on Windows XP 32-bits, Windows 7-32-bits, but in Windows Vista-32bits fails.
  On what i know it should work, or do you know any possible reason why it fails?
  Error Code(39).
• [email protected] wrote:
  > Is there any special thing installing inf files for a KMDF Driver in Windows Vista 32 bits?
  > I can install my driver in Windows XP-32, Windows 7-32, Windows Vista-64 and Windows 7-64, but i am no able to install on windows Vista 32 bits.
  HOW are you installing this, exactly?
  Given this section:
  [SourceDisksFiles.x86]
  dynambus.sys = 1,WINDOWSinf32
  lower_usb.sys = 1,WINDOWSinf32
  WdfCoInstaller01009.dll = 1,WINDOWSinf32
  The device manager is going to expect the following directory structure
  for your driver package:
  - bus_cdc_32_64.inf
  + windows
  + inf
  + 32
  - dynambus.sys
  - lower_usb.sys
  - WdfCoInstaller01009.dll
  + 64
  - dynambusV.sys
  - lower_usbV.sys
  - WdfCoInstaller01009.dll
  Do you see what I mean? In the same folder as the INF file, it will
  expect to find a folder called 'windows'. Inside that, it will expect
  to find a folder called 'inf'. The folder names in SourceDisksFiles
  sections are always relative to the folder that contains the INF.
  --
  Tim Roberts, [email protected]
  Providenza & Boekelheide, Inc.

  Tim Roberts, [email protected]
  Providenza & Boekelheide, Inc.

• >Do you see what I mean? In the same folder as the INF file, it will
  >expect to find a folder called 'windows'. Inside that, it will expect
  >to find a folder called 'inf'. The folder names in SourceDisksFiles
  >sections are always relative to the folder that contains the INF.
  Yes, i did it for have an easy install, so when the device is connected choose the recommended option and not do it step by step in the advanced mode(search for the inf file).
  I can install the driver for XP 32-bits and 7-32 bits with this inf, but i am no able to install on Windows Vista 32 bits.
  My question is why? ,if Windows XP,Vista,7 access to the same section and the same .sys, Windows Vista 32 can not be installed.
• Did you check if there are any clues in %systemroot%setupact.log?
  Kris
• On Mon, May 2, 2011 at 10:09 PM, Krzysztof Uchronski <[email protected]> wrote:
  > Did you check if there are any clues in %systemroot%setupact.log?
  Also did you make sure that you are not trying to load 64 bit binary
  on your 32 bit system?
  And if you run out of ideas I would also check whether hooking up KD +
  .kdfiles helps. This is really monkey-check but if it doesn't work
  then you can most likely exclude problems with
  signing/certificates/etc.
  Kris
• At 20:54 02/05/2011, [email protected] wrote:
  > >No, it certainly does not. Are you aware of the difference between an
  > >error and a warning?
  >
  >Yes, but i want to discard any possible warning or error to find the
  >way to install the driver on Windows Vista 32, because i do not find
  >a reason why the same inf files section and .sys files works right
  >on Windows XP 32-bits, Windows 7-32-bits, but in Windows Vista-32bits fails.
  >On what i know it should work, or do you know any possible reason
  >why it fails?
  >
  >Error Code(39).
  There's another common cause of code 39 (Driver not loaded due to
  corrupt or missing binary) which is nothing to do with the INF file
  or signing issues.
  Does the install copy your sys files to system32drivers ?
  If so, try running Depends.exe on your driver binary ? You may find
  that there's an exported function you expect in ntoskrn or other
  system library that isn't where you expect it to be on that version of Windows.
  Mark.
• [email protected] wrote:
  >
  > Yes, i did it for have an easy install, so when the device is connected choose the recommended option and not do it step by step in the advanced mode(search for the inf file).
  I'm not sure what that means. Did you put the INF file in the root of
  your disk, and then put the files in subdirectories of windowsinf?
  That is such an incredibly bad idea that I can't imagine you would have
  done it.
  If you are just testing, then who cares how many steps it takes? Vista
  will remember the location you last used for driver installs.
  > I can install the driver for XP 32-bits and 7-32 bits with this inf, but i am no able to install on Windows Vista 32 bits.
  > My question is why? ,if Windows XP,Vista,7 access to the same section and the same .sys, Windows Vista 32 can not be installed.
  I don't know, because you never tell us all of the facts. For example,
  this could be something as simple as a KMDF version issue, if you have
  the co-installer stuff messed up, or if you didn't copy the co-installer
  DLL properly. Windows 7 ships with KDMF 1.9. You might have installed
  something else on your XP system that brought it up to 1.9. Vista ships
  with 1.7, so your install will require a reboot to upgrade KMDF.
  You need to look at setupapi.app.log and setupapi.dev.log from the
  WindowsInf directory and see what they tell you. Post the entire
  applicable sections from those file, if you need to.
  --
  Tim Roberts, [email protected]
  Providenza & Boekelheide, Inc.

  Tim Roberts, [email protected]
  Providenza & Boekelheide, Inc.

• >There's another common cause of code 39 (Driver not loaded due to
  >corrupt or missing binary) which is nothing to do with the INF file
  >or signing issues.
  This looks more like my problem.
  >Does the install copy your sys files to system32drivers ?
  Yes.
  >If so, try running Depends.exe on your driver binary ? You may find
  >that there's an exported function you expect in ntoskrn or other
  >system library that isn't where you expect it to be on that version of Windows.
  I checked the Depends.exe and there is a section where 2 fields are in read that in difference from Windows XP those fields are correct (green) :
  WDFLDR.SYS - WdfVersionBindClass
  WdfVersionUnbindClass
  Does anything about this could cause that problem??
  Thanks.
• [email protected] wrote:
  >
  > I checked the Depends.exe and there is a section where 2 fields are in read that in difference from Windows XP those fields are correct (green) :
  >
  > WDFLDR.SYS - WdfVersionBindClass
  > WdfVersionUnbindClass
  >
  > Does anything about this could cause that problem??
  What does it say to YOU? This is an enormous hint, and it says that my
  previous comment was correct. Those two functions were not present in
  the 1.7 version of KMDF that shipped with Vista. That means that you
  are not running KMDF co-installer properly, so you are not upgrading to
  the 1.9 version of KMDF that you need.
  Going back to your INF file, you missed an obvious error:
  [DriverInstall32.ntx86.CoInstallers]
  CopyFiles=MyDevice_CoInstaller_CopyFiles
  AddReg=MyDevice_CoInstaller_AddReg
  [Driver64WV.ntamd64.Wdf]
  KmdfService = %DRIVERFILENAME%, MyDevice_wdfsect
  That section name is wrong. It should b e
  [DriverInstall32.ntx86.Wdf]. You just cut-and-pasted this from the
  64-bit section without checking. Further, you can't use
  %DRIVERFILENAME% here, because that's the 64-bit driver name. Here, you
  need
  [DriverInstall32.ntx86.Wdf]
  KmdfService = dynambus, MyDevice_wdfsect
  --
  Tim Roberts, [email protected]
  Providenza & Boekelheide, Inc.

  Tim Roberts, [email protected]
  Providenza & Boekelheide, Inc.

• Thanks Tim:
  Your right now i can install it.
  As you said the KMDF version for windows Vista is 1.7 by default, but is there any way to update KMDF version to 1.9 without the INF file?, because my intention is to install the driver as 'Recomended' copying the inf file in Windows/Inf, but if i try to do it as Recommended the installation fails because it needs to be rebooted to update to 1.9 KMDF version, in the other case if i install it in advance mode windows can ask for reboot the machine so the installation goes successfully.
  Thanks for all
• [email protected] wrote:
  > Your right now i can install it.
  > As you said the KMDF version for windows Vista is 1.7 by default, but is there any way to update KMDF version to 1.9 without the INF file?, because my intention is to install the driver as 'Recomended' copying the inf file in Windows/Inf, but if i try to do it as Recommended the installation fails because it needs to be rebooted to update to 1.9 KMDF version, in the other case if i install it in advance mode windows can ask for reboot the machine so the installation goes successfully.
  Look, if you want to install a driver, you follow the rules. People who
  don't follow the rules cause the kind of chaos that gives driver writers
  a bad name. You NEVER copy an INF file directly to WindowsINF. You
  must allow Windows to do that, through the normal installation APIs.
  So, what is the overall problem here? Is the problem that your device
  gets matched by a standard driver and you need to override it? There
  are ways to handle that. For example, 'devcon update' will do that, and
  you have the source for devcon if you want to copy the code to your own
  installer.
  --
  Tim Roberts, [email protected]
  Providenza & Boekelheide, Inc.

  Tim Roberts, [email protected]
  Providenza & Boekelheide, Inc.

• My problem is not copying the files, the problem is the next:
  When i plug my device a Wizard appear with 2 options:
  Install the software automatically.
  Install from a specific location.
  If i choose advance, then i search the inf file, the driver completes the installation and Windows ask for reboot the Computer with a successfully installation.
  But i want an easier installation, so i copy the inf file to Windows/inf (i will search about devcon to do it as it must), i choose install the software as Recommended, so windows search in /windows/inf/, it find the inf file but in the Windows Vista case, where a KMDF version is older that the neccesary (1.9) it must aks for a reboot to install the KMDF 1.9 as was declared in the INF, but in this case ('Recommended') it does not ask for a reboot, so it fails. So my question is, Can i update KMDF version to 1.9 in Vista before installing my driver? or any other option to install the driver automatically?
  Thanks.
• [email protected] wrote:
  > My problem is not copying the files, the problem is the next:
  >
  > When i plug my device a Wizard appear with 2 options:
  > Install the software automatically.
  > Install from a specific location.
  >
  > If i choose advance, then i search the inf file, the driver completes the installation and Windows ask for reboot the Computer with a successfully installation.
  >
  > But i want an easier installation, so i copy the inf file to Windows/inf .. So my question is, Can i update KMDF version to 1.9 in Vista before installing my driver? or any other option to install the driver automatically?
  I wish you had said some of this a long time ago. The RIGHT answer is
  for you to 'pre-install' your driver, using an application like 'devcon
  dp_add' or 'DPInst'. That copies your driver package into the 'driver
  store', and the driver store is one of the places that gets searched
  when you choose 'install the software automatically'.
  --
  Tim Roberts, [email protected]
  Providenza & Boekelheide, Inc.

  Convert pdf to dwg using bluebeam. Tim Roberts, [email protected]
  Providenza & Boekelheide, Inc.

Have you ever erased any of your important files thinking that they are not required? Since you deleted the file using “Shift + Delete” keyboard shortcut you couldn’t find that file in the Recycle Bin. Now what? No need to worry, you still have a chance to get it back. This article helps you retrieve your deleted files from Windows Vista hard drive instantly.

How can Deleted Files from Vista be Recovered?

Deleted files can be recovered, because whenever you delete any file from your Windows computer; the OS does not permanently delete them from your hard disk. It just deletes the index entry of the files and marks that storage space as empty, so that new data can be added to it. Unless those deleted files are not overwritten by any new files, those files are recoverable.

Prominent reasons for deletion of files from Windows Vista are as mentioned below:

• Accidental deletion of important file while freeing up hard disk space
• Erasing a file using “Shift + Delete” keys or from MS-DOS utility
• An unauthorized user deleting your file without your knowledge
• File conflicting with Vista OS resulting in file deletion
• Electro static power surge while accessing your file
• Virus infected files on Windows Vista can be removed by antivirus program
• Deleting a file of large size which fails to get stored in the Recycle Bin

If you have encountered any of the above mentioned scenarios that resulted in file deletion, don’t get frustrated. You can use File Recovery tool to get back.

Tool to Recover Deleted Files from Windows Vista-

You can take the aid of efficient file recovery software like Yodot File Recovery to restore files that are accidentally deleted from Windows Vista. It successfully recovers shift deleted files, files deleted from MS-DOS prompt or after emptying Windows Vista Recycle Bin. It not only helps users in retrieving deleted files from Windows Vista, but also helps in recovering lost or missing files and folders from Windows Vista. It also restores files from Windows Server 2003, 2008, Windows XP, Windows 7, Windows 8, Windows 10, aside Windows Vista. Along with hard drive you can get back deleted files and folders from external hard drives, USB drives, iPods, memory cards and other storage media on Windows PC.

Complete Guide to Recover Files from Windows Vista:

• Download and install Yodot File Recovery software on your computer
• Open the installed application to start the recovery process
• The main screen displays two options, “Deleted File Recovery” and “Lost File Recovery”
• Click on “Deleted File Recovery” option to retrieve your deleted files
• The application now scans and displays all the drives present in your Windows Vista system
• Choose the drive from where you want to recover your deleted files
• Once you select the partition, the tool starts scanning again and shows all the deleted files from the selected drive
• You can make use of the search box to search for a specific file
• The Red Cross mark displays the files which were deleted
• Choose the files that you want to recover and click on “Next” button
• At last, save the recovered files to your desired location

Suggestions:

• Stop using your Windows Vista computer after you realize that some of your files are deleted/lost
• Backup your important files on storage devices like CDs and DVDs
• Download and install antivirus program to make your Windows Vista system free from viruses or external threats
• Protect your important Office files or personal by making them as read-only

Useful links

Transfer Android SMS to PC or New Android. Users can transfer and backup text messages from Android phone to computer where messages can be easily viewed, edited, exported and printed out. You get a new Android phone and want to transfer SMS from old Android to new Android, this powerful SMS Backup for Android will always meet your needs. Android sms transfer to pc free download - AST Android SMS Transfer, Backuptrans Android SMS Transfer, AST Android SMS Transfer, and many more programs. With those programs, you can easily transfer Android text messages to a computer. It can be a Windows PC or Apple Mac computer. First, download and install the program on a computer; Then connect the phone to computer with USB cable. Find the backup option on the program and select the data type you wish to transfer. Android sms transfer free version download. System Utilities downloads - AST Android SMS Transfer by Android Phone SMS Backup & Restore and many more programs are available for instant and free download. Android sms transfer free download - AST Android SMS Transfer, AST Android SMS Transfer, Apolsoft Android SMS Transfer, and many more programs.

Support

Resources

Follow us on Social Media