Yes. I have a bug report for you. OEMSCAN has a tendency to match DRIVE MANUFACTURERS as well as system OEMs. So for example if you have a Toshiba notebook with an HP DVD drive and an IBM Hard drive, OEMSCAN would first match [HP] instead of [Toshiba]. Or [iBM] before [Toshiba]. Because the RANGE parameter varies between systems, the only way for us to temporarily cure this issue is to juggle the oemscan.ini entries to put the drive manufacturers last in the list, but we still sometimes have issues. I'm working on a "manual over-ride" addition to my batch script addon to manually select the OEM and pass it to OEMSCAN. I'd love for you to fix this bug. Or can you PM me so I can peek at the source code? Wasn't this project going open-source? Also, still waiting for a listing of available switches/commands OEMSCAN will accept. We know that oemscan.exe /d results in a "dry-run", but oemscan.exe /? brings up nothing at all. I can provide my batch file source to you upon request so you can see how it operates. Thanks in advance!