|
阅读：1361回复：9
installing imsamp without ncpa
所有留言及回应
Message 1 in thread 寄件者：Dan M. White (dwhite@tril-inc.com) 主旨：installing imsamp without ncpa 新闻群组：comp.os.ms-windows.programmer.nt.kernel-mode View this article only 日期：1998/10/06 I found a Microsoft article explaining how to install network components without using ncpa. I had already figured out what the article directed me to do, but it indicated that, if the bindings need to be done af ter the installation, it must be done manually from ncpa. We are creating a driver modeled after imsamp and my customer would reeeeeeeeeally like to do this without the ncpa. I think Netware got around this and I am hoping someone knows how to use setup.exe to finish installing imsamp. I need not only to get my bindings to happen, but to get a review bindings cycle going so TCP and NBINFO can review theirs, too. -- Help, Dan This page intentionally left bland. Message 2 in thread 寄件者：PN (pdrn@pacbell.net) 主旨：Re: installing imsamp without ncpa 新闻群组：comp.os.ms-windows.programmer.nt.kernel-mode View this article only 日期：1998/10/07 can you send me the info you have on installing the net components without ncpa ? we are looking for the same info. re: binding. There must be an api to the ncpa. any sample code / inf files you can let me see would be appreciated as well. much thanks pdrn@pacbell.net Message 3 in thread 寄件者：Jeffrey Goodwin (jeffg@osgroup.com) 主旨：Re: installing imsamp without ncpa 新闻群组：comp.os.ms-windows.programmer.nt.kernel-mode View this article only 日期：1998/10/08 Ashley Laurent has a complete toolkit to handle this for NT, and 95/98. It\'s plug and play, and can get you going fast. It also supports a wide range of network cards, Wan Cards, and dial up adapters. See www.osgroup.com for further details. Sincerely, Jeffrey Goodwin Dan M. White wrote in message <361A5B9A.BEEF2A30@tril-inc.com>... > > I found a Microsoft article explaining how to install network components >without using ncpa. I had already figured out what the article directed me >to do, but it indicated that, if the bindings need to be done af ter the >installation, it must be done manually from ncpa. > > We are creating a driver modeled after imsamp and my customer would >reeeeeeeeeally like to do this without the ncpa. I think Netware got around >this and I am hoping someone knows how to use setup.exe to finish installing >imsamp. > > I need not only to get my bindings to happen, but to get a review >bindings cycle going so TCP and NBINFO can review theirs, too. > > > >-- > Help, > Dan > > This page intentionally left bland. > > Message 4 in thread 寄件者：PDRN (pdrn@pacbell.net) 主旨：Re: installing imsamp without ncpa 新闻群组：comp.os.ms-windows.programmer.nt.kernel-mode View this article only 日期：1998/10/08 How much $$ is just the install portion ? Message 5 in thread 寄件者：msterr (msterr@fh-landshut.de) 主旨：Re: installing imsamp without ncpa 新闻群组：comp.os.ms-windows.programmer.nt.kernel-mode View this article only 日期：1998/10/26 Finally I am not alone with this probl.... Could you send me some infos, if you find something, thanks a lot. msterr@fh-landshut.de Message 6 in thread 寄件者：msterr (msterr@fh-landshut.de) 主旨：Re: installing imsamp without ncpa 新闻群组：comp.os.ms-windows.programmer.nt.kernel-mode View this article only 日期：1998/10/27 Dan M. White wrote<361A5B9A.BEEF2A30@tril-inc.com>... > > I found a Microsoft article explaining how to install network components >without using ncpa. I had already figured out what the article directed me >to do, but it indicated that, if the bindings need to be done af ter the >installation, it must be done manually from ncpa. > > We are creating a driver modeled after imsamp and my customer would >reeeeeeeeeally like to do this without the ncpa. I think Netware got around >this and I am hoping someone knows how to use setup.exe to finish installing >imsamp. > > I need not only to get my bindings to happen, but to get a review >bindings cycle going so TCP and NBINFO can review theirs, too. > Help, > Dan I found something in a KB-article from MS, most probably you will know this one already. Anyway, here it is: Keywords : ntsetup NTSrvWkst kbsetup Version : WinNT:3.51,4.0 Platform : winnt Issue type : kbinfo CAUTION: The solution included in this article has not been extensively tested in large installations. Microsoft cannot guarantee that modification of network components as recommended herein will accomplish the objective described in this article under all circumstances and in all configurations. (did they ever?-;) The Network Control Panel tool (loaded from a file called Ncpa.cpl) takes control over all setup of network components. When you add a network component through the interface, Ncpa.cpl tells Setup.exe to call Ncpashel.inf with specific parameters. Instead of using the Network Control Panel tool, it is possible to call Setup.exe with the following parameters: SETUP.EXE /f /i%systemroot%\\system32\\ncpashel.inf /T NTN_InstallMode = Install 观看文件全部内容 （仍有 38 行） ?2002 Google |
|
|
|
沙发#
发布于：2002-05-23 23:09
回应的第 1-10 项留言
后4项 跳到 [ 最新回应 ] Message 1 in thread 寄件者：hsam (hsengmfa12@hotmail.com) 主旨：driver installed 新闻群组：microsoft.public.development.device.drivers View this article only 日期：2002-02-28 10:25:43 PST Can someone give me full ideas how usually an win2k/xp IM driver get installed? How many inf files we need? Do we need snetcfg.dll or any provided dll to do something for us ? Thanks Sam Message 2 in thread 寄件者：Stephan Wolf (stewo68@hotmail.com) 主旨：Re: driver installed 新闻群组：microsoft.public.development.device.drivers View this article only 日期：2002-03-01 02:37:03 PST An NDIS IM (intermediate) requires two INF files: - one for the IM\'s protocol part - one for the IM\'s miniport part AFAIK, there is no \"usual\" way for an IM to get installed. There are several approaches: 1. Install the protocol part manually in \"Network and Dial-up connections\" - select a card - \"Properties\" - \"Install...\" - \"Protocol\" - \"Have Disk...\" - enter path to your IM files - select your protocol. In your protocol INF, make sure to copy the miniport INF and the Notify Object DLL (if any) If your IM is a \"filter\", installation of virtual adapters is done automatically by the system. If your IM is a \"MUX\", install any virtual Miniports as necessary from your Notify Object using INetCfg interface functions. 2. Write some installation application or a control panel applet (CPA) to install/configure your IM\'s protocol and virtual adapters using INetCfg interface functions. Hmm, SNETCFG is not a DLL, but an EXE. It is a command line tool to that demonstrates how to use the INetCfg COM interface. Also see the PASSTHRU and MUX samples in the DDK for details. Stephan --- On Thu, 28 Feb 2002 10:20:03 -0800, hsam <hsengmfa12@hotmail.com> wrote: >Can someone give me full ideas how usually an win2k/xp IM driver get >installed? >How many inf files we need? >Do we need snetcfg.dll or any provided dll to do something for us ? >Thanks >Sam Message 3 in thread 寄件者：Eliyas Yakub (eliyasy@microsoft.com) 主旨：Re: driver installed 新闻群组：microsoft.public.development.device.drivers View this article only 日期：2002-03-01 07:32:45 PST To add to this: Please follow only the XP DDK passthru sample. The Win2K passthru is buggy. You can conditionally compile the XP passthru to work on Win2K. > In your protocol INF, make sure to copy the miniport INF and the > Notify Object DLL (if any) > Please copy the miniport INF using CopyINF directive as shown in the XP version of the passthru sample. On Win2K, this directive is supported only on SP2 and above. So to workaround this limitation, the XP passthru notify object DLL during setup finds out the OS version at runtime and copies the INF file using SetupCopyOemINF function if it happens to run on Win2K SP1. -Eliyas \"Stephan Wolf\" <stewo68@hotmail.com> wrote in message news:3c7f56c3.3410904@news.t-online.de... > An NDIS IM (intermediate) requires two INF files: > > - one for the IM\'s protocol part > - one for the IM\'s miniport part > > AFAIK, there is no \"usual\" way for an IM to get installed. There are > several approaches: > > 1. Install the protocol part manually in \"Network and Dial-up > connections\" - select a card - \"Properties\" - \"Install...\" - > \"Protocol\" - \"Have Disk...\" - enter path to your IM files - select > your protocol. > > In your protocol INF, make sure to copy the miniport INF and the > Notify Object DLL (if any) > > If your IM is a \"filter\", installation of virtual adapters is done > automatically by the system. > > If your IM is a \"MUX\", install any virtual Miniports as necessary from > your Notify Object using INetCfg interface functions. > > 2. Write some installation application or a control panel applet (CPA) > to install/configure your IM\'s protocol and virtual adapters using > INetCfg interface functions. > > Hmm, SNETCFG is not a DLL, but an EXE. It is a command line tool to > that demonstrates how to use the INetCfg COM interface. > > Also see the PASSTHRU and MUX samples in the DDK for details. > > Stephan > --- > On Thu, 28 Feb 2002 10:20:03 -0800, hsam <hsengmfa12@hotmail.com> > wrote: > > >Can someone give me full ideas how usually an win2k/xp IM driver get > >installed? > >How many inf files we need? > >Do we need snetcfg.dll or any provided dll to do something for us ? > >Thanks > >Sam Message 4 in thread 寄件者：hsam (hsengmfa12@hotmail.com) 主旨：Re: driver installed 新闻群组：microsoft.public.development.device.drivers View this article only 日期：2002-03-04 09:58:51 PST Thanks all for the help. But still, one more question: In my system(2k), there is already an Network IM drivers installed (not mine) If I want to intercept(for display purpose ( readonly) ) the raw packets (ethernet packet, everything include headers),then what type of drivers should i write - miniport/protocol/im ? I think winsock raw socket is not possible. And please show me one sample from DDK so i can start with.. Thanks a lot. Appreciate it. Sam Eliyas Yakub wrote: > To add to this: > > Please follow only the XP DDK passthru sample. The Win2K passthru is buggy. > You can conditionally compile the XP passthru to work on Win2K. > > > In your protocol INF, make sure to copy the miniport INF and the > > Notify Object DLL (if any) > > > Please copy the miniport INF using CopyINF directive as shown in the XP > version of the passthru sample. On Win2K, this directive is supported only > on SP2 and above. So to workaround this limitation, the XP passthru notify > object DLL during setup finds out the OS version at runtime and copies the > INF file using SetupCopyOemINF function if it happens to run on Win2K SP1. > > -Eliyas > > \"Stephan Wolf\" <stewo68@hotmail.com> wrote in message > news:3c7f56c3.3410904@news.t-online.de... > > An NDIS IM (intermediate) requires two INF files: > > > > - one for the IM\'s protocol part > > - one for the IM\'s miniport part > > > > AFAIK, there is no \"usual\" way for an IM to get installed. There are > > several approaches: > > > > 1. Install the protocol part manually in \"Network and Dial-up > > connections\" - select a card - \"Properties\" - \"Install...\" - > > \"Protocol\" - \"Have Disk...\" - enter path to your IM files - select > > your protocol. > > > > In your protocol INF, make sure to copy the miniport INF and the > > Notify Object DLL (if any) > > 观看文件全部内容 （仍有 27 行） Message 5 in thread 寄件者：Stephan Wolf (stewo68@hotmail.com) 主旨：Re: driver installed 新闻群组：microsoft.public.development.device.drivers View this article only 日期：2002-03-04 12:01:02 PST You can install more than one NDIS intermediate driver (IM). You should write an IM. See the PASSTHRU sample in the XP DDK as already suggested. Stephan --- On Mon, 04 Mar 2002 09:55:03 -0800, hsam <hsengmfa12@hotmail.com> wrote: > >Thanks all for the help. >But still, one more question: >In my system(2k), there is already an Network IM drivers installed (not mine) >If I want to intercept(for display purpose ( readonly) ) the raw packets >(ethernet packet, everything include headers),then >what type of drivers should i write - miniport/protocol/im ? I think winsock >raw socket is not possible. >And please show me one sample from DDK so i can start with.. >Thanks a lot. Appreciate it. >Sam > > >Eliyas Yakub wrote: > >> To add to this: >> >> Please follow only the XP DDK passthru sample. The Win2K passthru is buggy. >> You can conditionally compile the XP passthru to work on Win2K. >> >> > In your protocol INF, make sure to copy the miniport INF and the >> > Notify Object DLL (if any) >> > >> Please copy the miniport INF using CopyINF directive as shown in the XP >> version of the passthru sample. On Win2K, this directive is supported only >> on SP2 and above. So to workaround this limitation, the XP passthru notify >> object DLL during setup finds out the OS version at runtime and copies the >> INF file using SetupCopyOemINF function if it happens to run on Win2K SP1. >> >> -Eliyas >> >> \"Stephan Wolf\" <stewo68@hotmail.com> wrote in message >> news:3c7f56c3.3410904@news.t-online.de... >> > An NDIS IM (intermediate) requires two INF files: >> > >> > - one for the IM\'s protocol part >> > - one for the IM\'s miniport part >> > 观看文件全部内容 （仍有 37 行） Message 6 in thread 寄件者：hsam (hsengmfa12@hotmail.com) 主旨：Re: driver installed 新闻群组：microsoft.public.development.device.drivers View this article only 日期：2002-03-04 16:17:12 PST Thank you very much. it\'s clear to me now. So if I install the passthru driver, if I want to insert it below the already installed im driver, what should i do ? OR if I want to insert it above the already installed im driver, what should i do ? Sam Stephan Wolf wrote: > You can install more than one NDIS intermediate driver (IM). > > You should write an IM. > > See the PASSTHRU sample in the XP DDK as already suggested. > > Stephan > --- > On Mon, 04 Mar 2002 09:55:03 -0800, hsam <hsengmfa12@hotmail.com> > wrote: > > > > >Thanks all for the help. > >But still, one more question: > >In my system(2k), there is already an Network IM drivers installed (not mine) > >If I want to intercept(for display purpose ( readonly) ) the raw packets > >(ethernet packet, everything include headers),then > >what type of drivers should i write - miniport/protocol/im ? I think winsock > >raw socket is not possible. > >And please show me one sample from DDK so i can start with.. > >Thanks a lot. Appreciate it. > >Sam > > > > > >Eliyas Yakub wrote: > > > >> To add to this: > >> > >> Please follow only the XP DDK passthru sample. The Win2K passthru is buggy. > >> You can conditionally compile the XP passthru to work on Win2K. > >> > >> > In your protocol INF, make sure to copy the miniport INF and the > >> > Notify Object DLL (if any) > >> > > >> Please copy the miniport INF using CopyINF directive as shown in the XP > >> version of the passthru sample. On Win2K, this directive is supported only > >> on SP2 and above. So to workaround this limitation, the XP passthru notify > >> object DLL during setup finds out the OS version at runtime and copies the > >> INF file using SetupCopyOemINF function if it happens to run on Win2K SP1. 观看文件全部内容 （仍有 48 行） Message 7 in thread 寄件者：Stephan Wolf (stewo68@hotmail.com) 主旨：Re: driver installed 新闻群组：microsoft.public.development.device.drivers View this article only 日期：2002-03-05 05:32:03 PST Try INetCfgComponentBindings::MoveBefore() INetCfgComponentBindings::MoveAfter() Stephan --- On Mon, 04 Mar 2002 16:13:26 -0800, hsam <hsengmfa12@hotmail.com> wrote: >Thank you very much. it\'s clear to me now. >So if I install the passthru driver, >if I want to insert it below the already installed im driver, what should i do ? >OR if I want to insert it above the already installed im driver, what should i do ? > >Sam Message 8 in thread 寄件者：hsam (hsengmfa12@hotmail.com) 主旨：Re: driver installed 新闻群组：microsoft.public.development.device.drivers View this article only 日期：2002-03-05 16:20:09 PST Thanks again, I will take alook on that. I wonder if you have ever used ethereal and sniffpro software. They are packet sniffers. When i installed them, i didn\'t see any new adapters or new protocols added to the network in the control panel. Why is that? Can u give me an explaination of what type of drivers those software use ? Sam Stephan Wolf wrote: > Try > > INetCfgComponentBindings::MoveBefore() > INetCfgComponentBindings::MoveAfter() > > Stephan > --- > On Mon, 04 Mar 2002 16:13:26 -0800, hsam <hsengmfa12@hotmail.com> > wrote: > > >Thank you very much. it\'s clear to me now. > >So if I install the passthru driver, > >if I want to insert it below the already installed im driver, what should i do ? > >OR if I want to insert it above the already installed im driver, what should i do ? > > > >Sam Message 9 in thread 寄件者：Stephan Wolf (stewo68@hotmail.com) 主旨：Re: driver installed 新闻群组：microsoft.public.development.device.drivers View this article only 日期：2002-03-05 16:43:03 PST Hmm, no, I have never heard of these. Anyway, you can set the NCF_HIDDEN characteristics flag in an INF to make any network component \"invisible\" to the user. From the docs: \"DDInstall Section for Network INF Files [..] NCF_HIDDEN Specifies that the component should not be shown in any user interface. \" HTH, Stephan --- On Tue, 05 Mar 2002 16:16:33 -0800, hsam <hsengmfa12@hotmail.com> wrote: >Thanks again, I will take alook on that. >I wonder if you have ever used ethereal and sniffpro software. >They are packet sniffers. When i installed them, i didn\'t see >any new adapters or new protocols added to the network >in the control panel. Why is that? Can u give me an explaination >of what type of drivers those software use ? >Sam > > > > > >Stephan Wolf wrote: > >> Try >> >> INetCfgComponentBindings::MoveBefore() >> INetCfgComponentBindings::MoveAfter() >> >> Stephan >> --- >> On Mon, 04 Mar 2002 16:13:26 -0800, hsam <hsengmfa12@hotmail.com> >> wrote: >> >> >Thank you very much. it\'s clear to me now. >> >So if I install the passthru driver, >> >if I want to insert it below the already installed im driver, what should i do ? >> >OR if I want to insert it above the already installed im driver, what should i do ? >> > >> >Sam > Message 10 in thread 寄件者：hsam (hsengmfa12@hotmail.com) 主旨：Re: driver installed 新闻群组：microsoft.public.development.device.drivers View this article only 日期：2002-03-06 13:42:46 PST I saw no NCF_HIDDEN in their inf file (only one inf file) But i saw a couple of drivers in their own directories Also i just saw a service added. No adapters, no protocols added.. --- Ok, forget them. So far you explain to me the way to install drvs in 2k/xp, how about winnt ? Can i use notifyobject to control the binding? Thanks Stephan Wolf wrote: > Hmm, no, I have never heard of these. > > Anyway, you can set the NCF_HIDDEN characteristics flag in an INF to > make any network component \"invisible\" to the user. From the docs: > > \"DDInstall Section for Network INF Files > [..] > NCF_HIDDEN > Specifies that the component should not be shown in any user > interface. \" > > HTH, Stephan > --- > On Tue, 05 Mar 2002 16:16:33 -0800, hsam <hsengmfa12@hotmail.com> > wrote: > > >Thanks again, I will take alook on that. > >I wonder if you have ever used ethereal and sniffpro software. > >They are packet sniffers. When i installed them, i didn\'t see > >any new adapters or new protocols added to the network > >in the control panel. Why is that? Can u give me an explaination > >of what type of drivers those software use ? > >Sam > > > > > > > > > > > >Stephan Wolf wrote: > > > >> Try > >> > >> INetCfgComponentBindings::MoveBefore() > >> INetCfgComponentBindings::MoveAfter() > >> > >> Stephan > >> --- > >> On Mon, 04 Mar 2002 16:13:26 -0800, hsam <hsengmfa12@hotmail.com> > >> wrote: > >> > >> >Thank you very much. it\'s clear to me now. > >> >So if I install the passthru driver, > >> >if I want to insert it below the already installed im driver, what should i do ? > >> >OR if I want to insert it above the already installed im driver, what should i do ? > >> > > >> >Sam > > -------------------------------------------------------------------------------- 后4项 跳到 [ 最新回应 ] ?2002 Google |
|
|
|
板凳#
发布于：2002-05-23 23:10
回应的第 11-14 项留言
前10项 跳到 [ 开始回应留言 ] Message 11 in thread 寄件者：Stephan Wolf (stewo68@hotmail.com) 主旨：Re: driver installed 新闻群组：microsoft.public.development.device.drivers View this article only 日期：2002-03-06 14:49:03 PST (Network) driver installation is completely diffrent on NT4. The INF format is completely different. Not sure, but I think there are no Notify Objects in NT4 either. Stephan --- On Wed, 06 Mar 2002 13:38:30 -0800, hsam <hsengmfa12@hotmail.com> wrote: > >I saw no NCF_HIDDEN in their inf file (only one inf file) >But i saw a couple of drivers in their own directories >Also i just saw a service added. >No adapters, no protocols added.. >--- >Ok, forget them. >So far you explain to me the way to install drvs in 2k/xp, >how about winnt ? Can i use notifyobject to control the binding? >Thanks > > > >Stephan Wolf wrote: > >> Hmm, no, I have never heard of these. >> >> Anyway, you can set the NCF_HIDDEN characteristics flag in an INF to >> make any network component \"invisible\" to the user. From the docs: >> >> \"DDInstall Section for Network INF Files >> [..] >> NCF_HIDDEN >> Specifies that the component should not be shown in any user >> interface. \" >> >> HTH, Stephan >> --- >> On Tue, 05 Mar 2002 16:16:33 -0800, hsam <hsengmfa12@hotmail.com> >> wrote: >> >> >Thanks again, I will take alook on that. >> >I wonder if you have ever used ethereal and sniffpro software. >> >They are packet sniffers. When i installed them, i didn\'t see >> >any new adapters or new protocols added to the network >> >in the control panel. Why is that? Can u give me an explaination >> >of what type of drivers those software use ? >> >Sam >> > 观看文件全部内容 （仍有 22 行） Message 12 in thread 寄件者：\"Eliyas Yakub\" (eliyasy@microsoft.com) 主旨：Re: driver installed 新闻群组：microsoft.public.development.device.drivers View this article only 日期：2002-03-07 13:51:04 PST Yep, there is no Intecfg interface on Windows NT4.0. NT4.0 network INFs use some kind of scripts to control the bindings during installation. Check the IMSamp INF files and the bindprune DLL to understand how it works. http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q178322 -- -Eliyas This posting is provided \"AS IS\" with no warranties, and confers no rights. You assume all risk for your use. -- Message 13 in thread 寄件者：shawn (shawn@att.com.SPAM1) 主旨：Re: driver installed 新闻群组：microsoft.public.development.device.drivers View this article only 日期：2002-03-29 10:23:01 PST If I\'m not using a Notify object and I need to be able to install to 2000, 2000 SP1, 2000 SP2, and XP, would I have to always use the cocpyinf.dll coinstaller? Is there a way to \"decorate\" my INF so the coinstaller is only used on 2000? Thanks, Shawn \"Eliyas Yakub\" <eliyasy@microsoft.com> wrote in message news:OlpuyXTwBHA.1312@tkmsftngp05... > To add to this: > > Please follow only the XP DDK passthru sample. The Win2K passthru is buggy. > You can conditionally compile the XP passthru to work on Win2K. > > > In your protocol INF, make sure to copy the miniport INF and the > > Notify Object DLL (if any) > > > Please copy the miniport INF using CopyINF directive as shown in the XP > version of the passthru sample. On Win2K, this directive is supported only > on SP2 and above. So to workaround this limitation, the XP passthru notify > object DLL during setup finds out the OS version at runtime and copies the > INF file using SetupCopyOemINF function if it happens to run on Win2K SP1. > > -Eliyas > > > \"Stephan Wolf\" <stewo68@hotmail.com> wrote in message > news:3c7f56c3.3410904@news.t-online.de... > > An NDIS IM (intermediate) requires two INF files: > > > > - one for the IM\'s protocol part > > - one for the IM\'s miniport part > > > > AFAIK, there is no \"usual\" way for an IM to get installed. There are > > several approaches: > > > > 1. Install the protocol part manually in \"Network and Dial-up > > connections\" - select a card - \"Properties\" - \"Install...\" - > > \"Protocol\" - \"Have Disk...\" - enter path to your IM files - select > > your protocol. > > > > In your protocol INF, make sure to copy the miniport INF and the > > Notify Object DLL (if any) > > > > If your IM is a \"filter\", installation of virtual adapters is done > > automatically by the system. > > 观看文件全部内容 （仍有 27 行） Message 14 in thread 寄件者：Eliyas Yakub (eliyasy@microsoft.com) 主旨：Re: driver installed 新闻群组：microsoft.public.development.device.drivers View this article only 日期：2002-03-29 13:05:23 PST >would I have to always use the cocpyinf.dll coinstaller? Why are you talking about coinstaller? You can\'t use coinstaller with IM drivers. You can only use notify object. >Is there a way to \"decorate\" my INF so the coinstaller is only used on 2000? You can only differentiate between Win2K (5.0) and XP (5.1) using Driver versioning decorations. AFIK, you can\'t differentiate between SPs. -- -Eliyas This posting is provided \"AS IS\" with no warranties, and confers no rights. \"shawn\" <shawn@att.com.SPAM1> wrote in message news:#G7V$401BHA.2684@tkmsftngp04... If I\'m not using a Notify object and I need to be able to install to 2000, 2000 SP1, 2000 SP2, and XP, would I have to always use the cocpyinf.dll coinstaller? Is there a way to \"decorate\" my INF so the coinstaller is only used on 2000? Thanks, Shawn \"Eliyas Yakub\" <eliyasy@microsoft.com> wrote in message news:OlpuyXTwBHA.1312@tkmsftngp05... > To add to this: > > Please follow only the XP DDK passthru sample. The Win2K passthru is buggy. > You can conditionally compile the XP passthru to work on Win2K. > > > In your protocol INF, make sure to copy the miniport INF and the > > Notify Object DLL (if any) > > > Please copy the miniport INF using CopyINF directive as shown in the XP > version of the passthru sample. On Win2K, this directive is supported only > on SP2 and above. So to workaround this limitation, the XP passthru notify > object DLL during setup finds out the OS version at runtime and copies the > INF file using SetupCopyOemINF function if it happens to run on Win2K SP1. > > -Eliyas > > 观看文件全部内容 （仍有 50 行） -------------------------------------------------------------------------------- 前10项 跳到 [ 开始回应留言 ] ?2002 Google |
|
|
|
地板#
发布于：2002-05-23 23:11
所有留言及回应
Message 1 in thread 寄件者：engban (engban@yahoo.com) 主旨：Help: Porting PASSTHRU sample to WinCE 新闻群组：comp.os.ms-windows.ce, comp.os.ms-windows.programmer.nt.kernel-mode View this article only 日期：2002-02-20 19:45:50 PST Hi all, I have seen people in the newsgroup successfully porting the IM driver from w2k to WinCE. However, when I try to port the PASSTHRU sample from w2k DDK to win ce, many errors were generated during the compilation. It seems to me that many functions and definations in the w2k are not defined for win ce. I am using eMbedded C++ 3.0 and Pocket PC 2002 sdk. Now, my questions are 1) Others than adding the export function, DriverEntry, in *.def file, what other things do I need to do? 2) or maybe it is not so easy as what they have claimed to be source code compatible? 3) they said I can find some samples in the eMbedded Tool kit, but I can\'t find any sample in network driver. Thanks for help in advance, engban Message 2 in thread 寄件者：weicco (marko.parkkola@netseal.com) 主旨：Re: Help: Porting PASSTHRU sample to WinCE 新闻群组：comp.os.ms-windows.ce, comp.os.ms-windows.programmer.nt.kernel-mode View this article only 日期：2002-02-21 02:20:59 PST engban@yahoo.com (engban) wrote in message news:<71f89fc4.0202201945.dc5978a@posting.google.com>... > Hi all, > > I have seen people in the newsgroup successfully porting the IM driver > from w2k to WinCE. However, when I try to port the PASSTHRU sample > from w2k DDK to win ce, many errors were generated during the > compilation. > > It seems to me that many functions and definations in the w2k are not > defined for win ce. > > I am using eMbedded C++ 3.0 and Pocket PC 2002 sdk. > > Now, my questions are > 1) Others than adding the export function, DriverEntry, in *.def file, > what other things do I need to do? > 2) or maybe it is not so easy as what they have claimed to be source > code compatible? > 3) they said I can find some samples in the eMbedded Tool kit, but I > can\'t find any sample in network driver. > > > Thanks for help in advance, > engban I think you need Windows CE Platform Builder if you are going to write drivers for PocketPC. Message 3 in thread 寄件者：engban (engban@yahoo.com) 主旨：Re: Help: Porting PASSTHRU sample to WinCE 新闻群组：comp.os.ms-windows.ce, comp.os.ms-windows.programmer.nt.kernel-mode View this article only 日期：2002-02-21 21:33:47 PST hi, But why do I need platform builder? I thought platform builder is only needed for customize OS? Do I need some kinds of library from the platform builder? I can find the ndis.h in the PocketPC 2002 SDK. The problem is that not all definitions in the w2k DDK (ndis.h) can be found in PocketPC 2002 SDK(ndis.h). Please advice me, thanks. engban marko.parkkola@netseal.com (weicco) wrote in message news:<c993f1dc.0202210220.67f7196e@posting.google.com>... > engban@yahoo.com (engban) wrote in message news:<71f89fc4.0202201945.dc5978a@posting.google.com>... > > Hi all, > > > > I have seen people in the newsgroup successfully porting the IM driver > > from w2k to WinCE. However, when I try to port the PASSTHRU sample > > from w2k DDK to win ce, many errors were generated during the > > compilation. > > > > It seems to me that many functions and definations in the w2k are not > > defined for win ce. > > > > I am using eMbedded C++ 3.0 and Pocket PC 2002 sdk. > > > > Now, my questions are > > 1) Others than adding the export function, DriverEntry, in *.def file, > > what other things do I need to do? > > 2) or maybe it is not so easy as what they have claimed to be source > > code compatible? > > 3) they said I can find some samples in the eMbedded Tool kit, but I > > can\'t find any sample in network driver. > > > > > > Thanks for help in advance, > > engban > > I think you need Windows CE Platform Builder if you are going to write > drivers for PocketPC. Message 4 in thread 寄件者：vani (vani_y@hotmail.com) 主旨：Re: Help: Porting PASSTHRU sample to WinCE 新闻群组：comp.os.ms-windows.ce, comp.os.ms-windows.programmer.nt.kernel-mode View this article only 日期：2002-02-21 17:36:55 PST 1. you would need to install the Platform Builder 3.0 for the SDK. 2. You do not need to write a seperate .DEF file for CE, simply export those Driver Entry Points using DLL Export macro 3. The platform builder installed does have the samples for NDIS driver, but not for passthru driver, for that you need to look into the samples of Windows NT or 2000. there will be compilation errors, as some of the NDIS functions are not available in CE. 4. you would need to use the platform builder SDK for the compilation. engban@yahoo.com (engban) wrote in message news:<71f89fc4.0202201945.dc5978a@posting.google.com>... > Hi all, > > I have seen people in the newsgroup successfully porting the IM driver > from w2k to WinCE. However, when I try to port the PASSTHRU sample > from w2k DDK to win ce, many errors were generated during the > compilation. > > It seems to me that many functions and definations in the w2k are not > defined for win ce. > > I am using eMbedded C++ 3.0 and Pocket PC 2002 sdk. > > Now, my questions are > 1) Others than adding the export function, DriverEntry, in *.def file, > what other things do I need to do? > 2) or maybe it is not so easy as what they have claimed to be source > code compatible? > 3) they said I can find some samples in the eMbedded Tool kit, but I > can\'t find any sample in network driver. > > > Thanks for help in advance, > engban ?2002 Google |
|
|
|
地下室#
发布于：2002-05-23 23:18
厉害。
|
|
|
|
5楼#
发布于：2002-05-23 23:22
build时顺便看看资料，如此而已.关上来大家看看,有用再说.heehee
|
|
|
|
6楼#
发布于：2002-05-23 23:25
build 什么那这么长时间？
|
|
|
|
7楼#
发布于：2002-05-23 23:29
不会告我说，在rebuild xp吧！
|
|
|
|
8楼#
发布于：2002-05-23 23:37
不会告我说，在rebuild xp吧！ 一般大的项目的预处理特别多，所以会BUILD很久的，我的可以坚持将近30多40秒~~P4的机子！ |
|
|
|
9楼#
发布于：2002-05-24 12:20
偶的机器太慢。PIII500+256M,足足要半个多小时，机器实在是太tmd的慢了。一定要找给2g的东东
|
|
|