Modify an old Device Driver for MISSIL 4302HD Mp4 Player?
in [Device Drivers]
|
Prev: Error in WdfRequestRetrieveOutputBuffer and WDF_MEMORY_DESCRIPTOR_INIT_BUFFER
Next: How do I dig deeper into a crash dump with WinDbg to idenify l
From: kcarring on 19 Dec 2009 18:57 I tried a different USB port, and this time, it did come up. It shows it as Drive Q. I was able to move some files to it this time. I'm now guessing there is no actual "control" software (though the book says there is, although it is rough translation from chinese). It allows one to move files, in it's "update mode" - but then if you hit a Mode button, you lose that ability.. and the device says "update is finished". so... I guess I was a bit fooled. Odd thing is, it doesn't seem to be charging, so I'll just leave it for a day hooked to this usb port, and then attempt to play a song etc. I think it may be working. When it "is" being recognized, I will also check out Device Manager and see if updating the driver is possible... when I looked, it had "disappeared" as explained above. Thanks for your help!
From: Tim Roberts on 20 Dec 2009 20:20 "Alexander Grigoriev" <alegr(a)earthlink.net> wrote: > >Windows 7 requires that the INF files are in UNICODE format. I'm not sure where you read this, but it's nonsense. Nothing has changed in this regard. >SourceDiskNames and SourceDiskFiles may also be mandatory now. dpinst, for >example, will fail without them. I'm not sure what to say about this. SourceDiskNames and SourceDiskFiles have always been mandatory, as infchk tells you. DPinst uses them to decide which files to copy to the driver store. I don't think anything has changed in this regard for the latest WDK. -- Tim Roberts, timr(a)probo.com Providenza & Boekelheide, Inc.
From: David Craig on 20 Dec 2009 20:51 I have noticed in the latest WDK that the samples provided do seem to have UNICODE source files. It is a real pain in some ways, but if you have language sensitive text, then it makes sense. "Tim Roberts" <timr(a)probo.com> wrote in message news:bvhti5d9k4s97b98td6fg35et6t1hae074(a)4ax.com... > "Alexander Grigoriev" <alegr(a)earthlink.net> wrote: >> >>Windows 7 requires that the INF files are in UNICODE format. > > I'm not sure where you read this, but it's nonsense. Nothing has changed > in this regard. > >>SourceDiskNames and SourceDiskFiles may also be mandatory now. dpinst, for >>example, will fail without them. > > I'm not sure what to say about this. SourceDiskNames and SourceDiskFiles > have always been mandatory, as infchk tells you. DPinst uses them to > decide which files to copy to the driver store. I don't think anything > has > changed in this regard for the latest WDK. > -- > Tim Roberts, timr(a)probo.com > Providenza & Boekelheide, Inc.
From: David Craig on 20 Dec 2009 21:49 Typing too fast. UNICODE inx files. Most source is still ASCII, I think. "David Craig" <drivers(a)noemail.noemail> wrote in message news:elH9sAegKHA.1112(a)TK2MSFTNGP04.phx.gbl... >I have noticed in the latest WDK that the samples provided do seem to have >UNICODE source files. It is a real pain in some ways, but if you have >language sensitive text, then it makes sense. > > "Tim Roberts" <timr(a)probo.com> wrote in message > news:bvhti5d9k4s97b98td6fg35et6t1hae074(a)4ax.com... >> "Alexander Grigoriev" <alegr(a)earthlink.net> wrote: >>> >>>Windows 7 requires that the INF files are in UNICODE format. >> >> I'm not sure where you read this, but it's nonsense. Nothing has changed >> in this regard. >> >>>SourceDiskNames and SourceDiskFiles may also be mandatory now. dpinst, >>>for >>>example, will fail without them. >> >> I'm not sure what to say about this. SourceDiskNames and SourceDiskFiles >> have always been mandatory, as infchk tells you. DPinst uses them to >> decide which files to copy to the driver store. I don't think anything >> has >> changed in this regard for the latest WDK. >> -- >> Tim Roberts, timr(a)probo.com >> Providenza & Boekelheide, Inc. > >
From: Tim Roberts on 22 Dec 2009 22:57
"David Craig" <drivers(a)noemail.noemail> wrote: > >I have noticed in the latest WDK that the samples provided do seem to have >UNICODE source files. It is a real pain in some ways, but if you have >language sensitive text, then it makes sense. Sure. Unicode is ALLOWED in INF files, as it always has been. Alexander said Unicode was now REQUIRED. That's nonsense. -- Tim Roberts, timr(a)probo.com Providenza & Boekelheide, Inc. |