Thread: [Ndiswrapper-general] (no subject) (Page 2)
Status: Beta
Brought to you by:
pgiri
From: Pawel <pa...@gr...> - 2005-03-07 02:18:19
|
=2D-=20 Pawel M=FCller Gitarrist Tel.: 0176 / 24075021 Bachstr. 32 70563 Stuttgart URL: http://www.groove-yard.de |
From: Ethan P. <ep...@ep...> - 2005-04-16 02:40:10
|
I've installed ndiswrapper (shows up in lsmod), used ndiswrapper to install bcmwl5.inf as my driver, and lspci and iwconfig report my card, but I cannot associate with my essid. I have gone through the troubleshooting FAQ, and I can get to "iwlist wlan0 scan," and it shows my network, but iwconfig doesn't associate with my router's ESSID (and redhat-config-network gives me "Determining IP address for wlan0 ... [long delay] failed"), and the LED in the card doesn't light up. Any ideas? |
From: Marco <ro...@we...> - 2005-11-08 19:11:45
|
From: steve b. <squ...@ho...> - 2005-11-13 21:05:28
|
I'm having trouble with my driver for my Broadcom 14E4:4320 (rev 3) WiFi. I'm on a Gateway 7330 laptop I installed the wrong driver 'netbc564' (64 bit) and got this after trying dmesg: ndiswrapper version 1.3rc1 loaded (preempt=yes,smp=no) ndiswrapper (check_nt_hdr:162): Windows driver is not 32-bit; bad magic: 020B ndiswrapper (load_sys_files:481): unable to prepare driver 'netbc564' ndiswrapper (ndiswrapper_load_driver:93): loadndiswrapper failed (11); check system log for messages from 'loadndisdriver' SO, I went and installed a different driver (bcmwl5), but I get the SAME MESSAGE as above after I load the modules and everything. It seems like it is still trying to look for 'netbc564' even though I uninstalled it... root@ubuntu:~$ ndiswrapper -l Installed ndis drivers: bcmwl5 driver present, hardware present bcmwl5a driver present, hardware present I've been trying to get this going for a week now...(Linux Noob)what do I do? What is wrong? Squivo |
From: engage <en...@n0...> - 2005-11-13 21:23:42
|
64 bit drivers won't work on a 32 bit machine. You need to uninstall them and then install the 32 bit XP drivers. I would recommend upgrading to ndiswrapper 1.5 also. On Sunday 13 November 2005 02:03 pm, steve barnett wrote: >I'm having trouble with my driver for my Broadcom 14E4:4320 (rev 3) WiFi. >I'm on a Gateway 7330 laptop > > >I installed the wrong driver 'netbc564' (64 bit) and got this after trying >dmesg: > >ndiswrapper version 1.3rc1 loaded (preempt=yes,smp=no) >ndiswrapper (check_nt_hdr:162): Windows driver is not 32-bit; bad magic: >020B >ndiswrapper (load_sys_files:481): unable to prepare driver 'netbc564' >ndiswrapper (ndiswrapper_load_driver:93): loadndiswrapper failed (11); check >system log for messages from 'loadndisdriver' > >SO, I went and installed a different driver (bcmwl5), but I get the SAME >MESSAGE as above after I load the modules and everything. It seems like it >is still trying to look for 'netbc564' even though I uninstalled it... >root@ubuntu:~$ ndiswrapper -l >Installed ndis drivers: >bcmwl5 driver present, hardware present >bcmwl5a driver present, hardware present > >I've been trying to get this going for a week now...(Linux Noob)what do I >do? What is wrong? > >Squivo |
From: Master S. <sha...@ar...> - 2005-12-01 06:43:35
|
Hi! I long to know if you plan that the ndiswrapper will assist the MA111= =20 USB-WLAN-Stick (Version 2). I think many people own this WLan Stick and =20 would like to use it on Linux but theres no way to use it. I hope you wil= l =20 code soon a resolution Cu MasterShadow --=20 Lieber langsam in die richtige Richtung, als beh=E4nde ins Verh=E4ngnis gehn! "Es gibt nur eine M=F6glichkeit zu lernen", entgegnete der Alchimist."Und= =20 das ist duch Handeln." (Der Alchimist von Paul Coelho) |
From: Markus F. <m....@mp...> - 2005-12-01 07:19:19
|
This stick should work with ndiswrapper, but it uses the prism2 chip and those chips are supported via wlan-ng and that would be the preferred way of using this stick. http://www.linux-wlan.org Am Donnerstag, 1. Dezember 2005 07.47 schrieb Master Shadow: > Hi! I long to know if you plan that the ndiswrapper will assist the MA111 > USB-WLAN-Stick (Version 2). I think many people own this WLan Stick and > would like to use it on Linux but theres no way to use it. I hope you will > code soon a resolution > > Cu MasterShadow |
From: Gerhard F. <nos...@gm...> - 2005-12-28 23:58:01
|
Dear Ndiswrapper Guys, I'm using the ndiswrapper on my Fujitsu-Siemens Amilo 1667G with the BCMWL5A driver, and basically the WLAN works fine. My notebook has a hardware RF switch. If I turn the switch off, then the interface disconnects from the AP. However, if I later turn the switch on again, then the interface does not automatically reconnect to the AP. It also looks like the interface forgets the configured ESSID, when it disconnects from the AP. Only if I explicitly reconfigure the ESSID again after turning on the hardware RF switch, I'm reconnected to the AP again. This is not an unsolvable problem, but it is uncomfortable. Is there any possibility to get the interface automatically (re)connected to the AP, if the RF switch is turned on again? Thanks, Gerhard -- Gerhard Fuernkranz gf...@us... -- Gerhard Fuernkranz nos...@gm... Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko! Satte Provisionen für GMX Partner: http://www.gmx.net/de/go/partner |
From: Giridhar P. <gi...@lm...> - 2006-01-05 17:41:07
|
On Thu, 29 Dec 2005 00:57:51 +0100 (MET), "Gerhard Fuernkranz" <nos...@gm...> said: Gerhard> problem, but it is uncomfortable. Is there any possibility Gerhard> to get the interface automatically (re)connected to the AP, Gerhard> if the RF switch is turned on again? ndiswrapper can't know when the switch is turned on, so it can't configure the interface. -- Giri |
From: Gerhard F. <nos...@gm...> - 2006-01-05 22:07:27
|
> --- Ursprüngliche Nachricht --- > Von: Giridhar Pemmasani <gi...@lm...> > > Gerhard> problem, but it is uncomfortable. Is there any possibility > Gerhard> to get the interface automatically (re)connected to the AP, > Gerhard> if the RF switch is turned on again? > > ndiswrapper can't know when the switch is turned on, so it can't > configure the interface. Yes, it can't know, and I also do not want it to know about about the switch at all. The idea is rather to continuously try to contacyt the AP and to (re)establish the link automatically whenever the network adapter gets radio contact to the AP, and to disconnect the link whenever radio contact is lost. I guess, there is no need to care, why the radio contact can be established or why it is lost. If the network interface would (re)establish the link automatically (to the ESSID set with iwconfig) whenever a radio connection to the AP is possible, then likely ifplugd could be used to ifconfig the interface at IP level whenever the radio link comes up, and to unconfigure it when the radio connection goes away (in the same way as ifplugd configures or unconfigures a wired ethernet interface, when the ethernet cable is plugged in or out). As ndiswrapper works currently, I have the impression that the network adapter does NOT continuously attempt to reconnect to the AP atomatically, when the radio connection gets lost, and it even looks like the network interface forgets the configured ESSID, when the radio connection is lost (at least, after a link loss, iwconfig does no longer display the ESSID I had configured previously, when the AP was still reachable). Regards, Gerhard -- Gerhard Fuernkranz nos...@gm... Telefonieren Sie schon oder sparen Sie noch? NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie |
From: Giridhar P. <gi...@lm...> - 2006-01-06 00:30:40
|
On Thu, 5 Jan 2006 23:07:16 +0100 (MET), "Gerhard Fuernkranz" <nos...@gm...> said: Gerhard> about the switch at all. The idea is rather to continuously Gerhard> try to contacyt the AP and to (re)establish the link That is not to be done in the driver. If you want, you can do that from user space. wpa_supplicant can do this, for example. -- Giri |
From: David J. <kc...@ho...> - 2006-05-02 21:41:13
|
when attempting to install drivers in ndiswrapper. I get the following = return. couldn't copy /media/cdrom/driver/winxp/rt61.inf at vsr/sbin/ndiswrapper line 144.=20 ndiswrapper reports rt61.inf installed and invalid. an attempt to = remove the driver returns that the driver is not installed. Wireless card is a zonet zew6101 with a raynet 2561 chipset. Thanks. |
From: Jim C. <jim...@gm...> - 2006-05-02 22:02:23
|
David Jackson wrote: > *when attempting to install drivers in ndiswrapper. I get the > following return.* > ** > *couldn't copy /media/cdrom/driver/winxp/rt61.inf* > *at vsr/sbin/ndiswrapper line 144. * > ** > * ndiswrapper reports rt61.inf installed and invalid. an attempt to > remove the driver returns that the driver is not installed.* > ** > * Wireless card is a zonet zew6101 with a raynet 2561 chipset.* > ** > *Thanks.* 'invalid driver' means that some of inf, conf, or sys are missing. it wont uninstall with the tool, cuz it doesnt look installed. delete /etc/ndiswrapper/zew6101/ to repair and retry. -e should probably clean up partials installs too. |
From: Jim C. <jim...@gm...> - 2006-05-03 00:21:19
|
David Jackson wrote: lets keep this on the list. Who knows, someone may search for "invalid driver" and find this thread. And dont top-post - to see why, read the 1st sentence below, and tell me what 'that' is. > I was wondering if that was a problem. The winxp folder has two inf > files and two sys files. Is there an order or priority to this > installation, or a command to install all files at once? > the INF files tell a windows installer what to do - and theyre pretty complicated to my eye. ndiswrapper parses it to find which files to install, and what parameters to collect into the conf files for use by ndiswrapper.ko If you want to start guessing, you could _probably_ just copy them all in manually, after running ndiswrapper to write the conf files, but.. I think you should: delete /etc/ndiswrapper, choose one of the INFs, run it as before ls -lR /etc/ndiswrapper, save listing to file. ndiswrapper -l should say driver installed hardware present if no hardware, then try -d devid drivername (devid from lspci -vn) test card if it doesnt work, -e it (or delete manually), try with other INF. if both dont work, then turn on debug (see the wiki), and repeat. > I'll try your delete proceedure, however linux never saw the card, whats that mean ? does lspci or lsusb not see the card ? if not youre sunk - linux must see the device b4 its usable. is your card on the wiki ? Giri, is there a way to add the wiki link to the ML footers ? > nor was it working. I found this information on the card itself, and > in the packaged literature. > u should use drivers listed on wiki, unless there arent any listed. If you get it working, pls report here, and add it to wiki. > Thanks for your quick reply. Your help is greatly appreciated. Thanks > again! > no prob. just recognize theres a quid-pro-quo. (ie the wiki) > Sincerely, > David Jackson > ----- Original Message ----- From: "Jim Cromie" <jim...@gm...> > To: "David Jackson" <kc...@ho...> > Cc: <ndi...@li...> > Sent: Tuesday, May 02, 2006 17:02 > Subject: Re: [Ndiswrapper-general] (no subject) > > >> David Jackson wrote: >>> *when attempting to install drivers in ndiswrapper. I get the >>> following return.* >>> ** *couldn't copy /media/cdrom/driver/winxp/rt61.inf* >>> *at vsr/sbin/ndiswrapper line 144. * >>> ** * ndiswrapper reports rt61.inf installed and invalid. an attempt >>> to remove the driver returns that the driver is not installed.* >>> ** * Wireless card is a zonet zew6101 with a raynet 2561 chipset.* >>> ** *Thanks.* >> >> 'invalid driver' means that some of inf, conf, or sys are missing. >> it wont uninstall with the tool, cuz it doesnt look installed. >> delete /etc/ndiswrapper/zew6101/ to repair and retry. >> -e should probably clean up partials installs too. >> > |
From: Jonathan B. <be...@gm...> - 2006-05-03 06:20:23
|
On 5/2/06, David Jackson <kc...@ho...> wrote: > > when attempting to install drivers in ndiswrapper. I get the following > return. > > couldn't copy /media/cdrom/driver/winxp/rt61.inf > at vsr/sbin/ndiswrapper line 144. > > ndiswrapper reports rt61.inf installed and invalid. an attempt to remove > the driver returns that the driver is not installed. > > Wireless card is a zonet zew6101 with a raynet 2561 chipset. Hmm, did you mean zew1601? 'cause that's all I can find on the Zonet website that was close to that. Have you tried downloading the driver from their website and using that driver? http://www.zonetusa.com/DispProduct.asp?ProductID=3D161 You also might copy all files from the CD to harddisk, and try to install the driver from there, just in case. I also find no mention of that specific card in the ndiswrapper wiki list, so it's possible that it doesn't work with ndiswrapper for some reason. Looking at the driver from Zonet, it has the name rt2500. Doing a Google search turns up Ralink, which may be the chipset, rather than raynet. I also found this: http://rt2x00.serialmonkey.com/wiki/index.php/Main_Page which you might want to give a try if that is the case. Jonathan |
From: David J. <kc...@ho...> - 2006-05-03 08:37:23
|
----- Original Message ----- From: "Jonathan Berry" <be...@gm...> To: "David Jackson" <kc...@ho...> Cc: <ndi...@li...> Sent: Wednesday, May 03, 2006 01:13 Subject: Re: [Ndiswrapper-general] (no subject) On 5/2/06, David Jackson <kc...@ho...> wrote: > > when attempting to install drivers in ndiswrapper. I get the following > return. > > couldn't copy /media/cdrom/driver/winxp/rt61.inf > at vsr/sbin/ndiswrapper line 144. > > ndiswrapper reports rt61.inf installed and invalid. an attempt to remove > the driver returns that the driver is not installed. > > Wireless card is a zonet zew6101 with a raynet 2561 chipset. Hmm, did you mean zew1601? 'cause that's all I can find on the Zonet website that was close to that. Have you tried downloading the driver from their website and using that driver? http://www.zonetusa.com/DispProduct.asp?ProductID=161 You also might copy all files from the CD to harddisk, and try to install the driver from there, just in case. I also find no mention of that specific card in the ndiswrapper wiki list, so it's possible that it doesn't work with ndiswrapper for some reason. Looking at the driver from Zonet, it has the name rt2500. Doing a Google search turns up Ralink, which may be the chipset, rather than raynet. I also found this: http://rt2x00.serialmonkey.com/wiki/index.php/Main_Page which you might want to give a try if that is the case. Jonathan Am I getting THAT dyslexic??? No wonder I can't get this straightened out!! Yes, the card is a zonet zew1601, and yes, the raylink chipset is 2561. Thanks, Jonathan. I saved the serialmonkey website, and I'll try tomorrow. Thanks again David Jackson |
From: taojiaqi <tao...@si...> - 2006-05-28 18:36:05
|
绝对不许杜邦侮辱中国的国格、中国人的人格来赖帐! 美国杜邦和贺利得太无耻,太无赖,欺人太甚! 加入WTO以来我国因知识产权赔偿超10亿美元 http://www.sina.com.cn 2006年04月27日17:03 新华网 新华网快讯:科技部部长徐冠华说,加入WTO以来,我国企业因知识产权纠纷引发的经济赔偿累计超过10亿美元,有些纠纷对有关产业甚至形成毁灭性打击。 ................................................................................................. 中美等国通过《上海宣言》共打知识产权犯罪 http://www.sina.com.cn 2006年04月01日17:42 新华网 新华网上海4月1日电题:《上海宣言》通过展现中国保护知识产权坚定决心 "近年来,中国在打击侵犯知识产权犯罪方面取得明显进展。公安机关自2000年至2005年,共破获侵犯知识产权犯罪案件6700余起,缉捕犯罪嫌疑人9300余人,涉案总价值近35亿元,对试图侵犯知识产权法的不法分子产生巨大威慑力,受到各国际组织、各国政府机构充分肯定和高度关注。 与此同时,中国已建立了包括刑事执法保护在内的、比较健全的知识产权法律体系和保护机制。除侵犯专利罪和销售侵权复制品罪的刑罚幅度是3年以下有期徒刑或拘役以外,其他5种侵犯知识产权犯罪最高均可处7年有期徒刑。同时,对所有这些犯罪,均可单处或者并处罚金。" 中国如此打击侵犯知识产权犯罪,保护美国知识产权!那麽美国应该怎麽办?美国在保护中国知识产权吗? 中国人再不是一盘散沙,根据“来而不往非礼也”的原则我们中国人应该怎麽办? 敬致中华人民共和国人民政府公务员同志们,同胞们。 (附: 敬致美国总统布什先生的公开信) 说明: 美国杜邦化学公司在2005年多次要求将杜邦和我方的争议提请仲裁机关裁决。我方尊重杜邦这一要求,在2006.01.16.给杜邦公司用挂号信寄去了《仲裁协议》版本。并附信说,杜邦如无异议,请杜邦在30天内签字、盖章后,保留一份,将其余二份寄回。杜邦如有异议,请提出杜邦的版本。并在2006.01.26.,2006.02.06.,2006.02.10.,2006.02.15.,将此《仲裁协议》和信件24次发送给了inf...@ch...和in...@du...。但是现在已经远远超过了30天,即已经远远超过了作出论证和决定的必要时间,仍无任何答复。这是杜邦企图继续赖帐的又一恶作剧表演,故发此e-mail麻烦各位,敬请谅解。如有可能,敬请您教育和强制杜邦不要继续玩这种赖帐的恶作剧表演了。 尊敬的人民的公务员同志,尊敬的同胞们, 各位好! 我的朋友黄**是中华人民共和国一项专利技术的专利权人。1995年美国杜邦以完全由杜邦公司单方面制订、未与黄**作任何协商的《1995年协议》独家占有了黄**一项高效、无毒的农业杀虫剂技术之后,一直拒绝按照杜邦在《1995年协议》第5条中主动承诺,付给黄**技术转让费或“完全赔偿”金。尤其恶劣的是,杜邦全球总 部董事会主席兼首席执行官贺利得(Holliday,霍尼迪)为了达到顽固赖帐的目的,三次在“REFUSED”(拒收)的黄先生信封正面污蔑黄先生是无赖分子,中华人民共和国(P・R・China中国)是无赖国家;黄**作为中华 人民共和国公民,根本没有资格像其他国家公民一样,根据世界各文明国家的法律和文明人类的惯例向杜邦主张自己的权利。 自2000年夏天以来,黄**几百次以纸质信件、传真、电话、E-mail、当面交涉等方式,提出了美国杜邦化学公司必须履行协议或完全赔偿的充足的事实证据与无可辩驳的法律依据;与此完全相反,美国杜邦化学公司提不出任何不履行协议或完全赔偿的事实证据与法律依据,但就是“绝对不”履行协议或完全赔偿,“你愿意怎么办就怎么办”。请问各位,到底谁是无赖(而且是跨国级的!)?贺利得具有的是什么样的资格?综上所述,毫无疑问,只有贺利得和美国杜邦才是无赖!确切地说,贺利得是强横无耻型的跨国级的无赖份子,美国杜邦是强横无耻型的跨国级的无赖公司。 美国杜邦公司和贺利得之流在欧、美等国敢如此狂妄傲慢、强横无理吗?不敢!其原因不言自明。因此,敬请您――尊敬的中华人民共和国人民政府人民的公务员同志,尊敬的同胞们, 为了捍卫国家的尊严,为了保护公民的合法权益,以自己的合法方式敦促美国政府加强对中方知识产权保护的执法力度,打击美国杜邦和贺利得强横无耻地强占黄**的知识产权的行为,强制杜邦履行在协议中主动承诺的义务。 我认为,我的这一请求并不过分:中美两国是平等的,中国政府有义务加强知识产权保护的执法力度保护美国人的知识产权;美国政府同样有义务加强知识产权保护的执法力度保护中国人的知识产权。 我们应该克服潜意识和思维定势中的自卑思想。中华人民共和国公民应该(因此也就必须)和世界任何国家的公民一样享有世界各文明国家的法律和文明人类的惯例所赋于的一切权利,其中当然包括知识产权。 中国的国情是什麽?是和世界上其他190个国家中任何一个国家都完全平等的伟大的中华人民共和国! 杜邦到中国来投资绝对不等于杜邦和贺利得可以侮辱中国的国格和强占中国公民的权利,绝对不等于杜邦和贺利得可以侮辱黄**的人格和强占黄**的知识产权。 美国杜邦和贺利得在中国如此目无一切地侮辱中国的国格、强横无耻地强占黄**的知识产权,绝对不行!中国人绝对必须根据世界各文明国家的法律和文明人类的惯例向杜邦主张自己的权利。 我们愿意和应该同杜邦、贺利得合作,但必须以平等互利为基础。 此致 最崇高的敬礼! 全责代理人:SXF (附件) 一 摘要 1. 从1993年4月起到1994年,黄先生应杜邦要求,向杜邦提供了近10次文字技术资料,供杜邦专家组进行可行 性分析。 2. 1995年2月22日杜邦技术转让与许可证经理Sklar博士 (E.I.DU PONT DE NEMOURS AND COMPANY Robert F. Sklar Ph. D. Manager,Technology Transfer Licensing)来中国上海,要与黄先生“签订许多协议”。黄 先生坚持要在让杜邦看了样品后再签协议,而当时样品尚在提纯过程中,故未签协议。 3. 1995年3月28日黄先生向杜邦寄出了第壹批样品。 4. 1995年9月7日黄先生收到杜邦寄来的《BIOLOGICAL EVALUATION AGREEMENT(生物效应鉴定协议,简称1995年协议),要求黄先生签署此协议并再提供样品。黄先生按杜邦要求签署了此协议并向杜邦寄出了第贰批样品 。杜邦在《1995年协议》第5条中向黄先生主动承诺,黄先生将有提取专利费、许可证费的权利。杜邦在《1995年协议》第8条中规定,黄先生不得与任何大学或企业等第三方作任何合作(黄先生为此而谢绝了几家公司要求合作的请求)。 5. 1998年9月10日杜邦发信向黄先生要到了第叁批样品。 6. 1999年杜邦对第叁批样品进行1个多月的Insecticide Screening(“杀虫剂筛选试验”,际实上,同时进行了杂草杀灭试验和霉菌杀灭试验。杜邦要求对这些试验全部保密)。 7. 2000年6月8日杜邦发信称对黄先生的样品不感兴趣,拒绝向黄先生支付专利费和特许证费。 8.2005.06.02. 杜邦签署信件,对黄先生进行威胁-恫吓,不准黄先生发此E-mail维护自己的合法权利。 说明:杜邦必须赔偿的法律依据 《中华人命共和国合同法》第107条规定:“当事人一方不履行合同义务或者履行合同义务不符合约定的,应当承担继续履行、......或者赔偿损失等违约责任。”(其他国家法律也有相同规定) 杜邦和我方签订了有效协议《生物效应鉴定协议(BIOLOGICAL EVALUATION AGREEMENT)》。 根据此协议我方向杜邦提供了一项高效、无毒的农业杀虫剂专利技术,可是杜邦并没有根据此协议履行向我方支付专利费和特许证费的义务;杜邦通知我方对我方技术“不感兴趣”的时间也比此协议规定的“九(9)个月内”晚了四十多个月,履行合同义务不符合约定。因此,杜邦必须依法向我方支付专利费和特许证费,或者支付等额赔偿金。 (附)敬致美国总统布什先生的公开信 An open letter to American President Mr. Bush 敬致美国总统布什先生的公开信 美国杜邦和贺利得是强横无耻型的跨国级的无赖! 我们敬请美国政府加强知识产权保护的执法力度,强制杜邦履行在协议中主动承诺的义务。 尊敬的布什总统先生,您好! 杜邦公司不履行协议的事实已多次通过pre...@wh...向您呈述;pre...@wh...也在 2004年9月代替总统先生发来下述三封内容相同的回信:“Thank you for e-mailing President Bush. Your ideas and comments are very important to him.”我的“ideas and comments”是黄先生有充足的事实证据与无可辩驳的法律依据证明,杜邦必须向黄先生支付专利费、许可证费或等额的“完全赔偿”金,杜邦一直拒绝支付这些费用是侵犯黄先生的知识产权。pre...@wh...说“are very important to him.” “very important”对总统先生是何含意,我不敢妄自猜测;但就愚见而言,有下列“important” 。 1.尊敬的总统先生和总统先生领导的美国政府以及伟大的美国人民对靠盗窃、靠耍无赖等无耻方法掠夺别人的知识产权深恶痛绝,而杜邦却正在干此无耻、无赖的勾当。 2.贵国在各种领域拥有的知识产权数量都远远超过世界任何一个国家,深受侵权之害。因此,历来的贵国政府都不遗余力敦促世界其他国家加强保护贵国知识产权的执法力度。但杜邦却用各种极其无耻的无赖手段侵犯黄先生的知识产权,这对世界其他国家的政府和公众将是一个极坏的信号,其他国家的公司和公众将误认为他们完全有权利以杜邦公司为榜样侵犯贵国的知识产权,如盗版音像制品、仿冒商标、剽窃专利技术。对贵国政府保护贵国知识产权的工作是一个极大的破坏,对贵国在世界上崇高地位是一个极大的耻辱。为了伟大美国人民的光荣,为了众多美国公司的声誉,为了保卫贵国在世界上的崇高地位,为了保护贵国和世界其他国家知识产权,敬请您和您的政府阻止杜邦的这种极其无耻的侵犯甚至强占行为,强制杜邦履行在协议中主动承诺的义务。 我们坚信,美国不是一个包庇和纵容无赖的国家,美国政府不是一个包庇和纵容无赖的政府;杜邦这个无赖在尊敬的总统先生和美国政府的教育下,是会懂得羞耻的,是能够改掉无赖行为成为一个正常的公司的。 由于事实证据充足,杜邦和黄先生双方的权利和义务明确,法律关系简单,所以只要贵国政府也加强知识产权保护的执法力度,杜邦公司对黄先生的知识产权的侵犯是完全可以阻止的,杜邦公司肯定会向黄先生支付专利费、许可证费或等额的“完全赔偿”金的。 此致 最崇高的敬礼! 全责代理人:SXF 2005.09.17.23:59 (附件,同上) An open letter to American President Mr. Bush(略) (求证E-mail:美国白宫总统E-mail pre...@wh... 杜邦中国 inf...@ch... , 杜邦总部Contact Us:in...@du... http://www1.dupont.com/NASApp/dupontglobal/corp/contactEmail.jsp) ************************************************************************************************ * 请大家都来唱: * * 无耻美国杜邦,卑鄙之极赖帐,跑到中国耍赖,在全世界出洋像!!!!!!!!!!!!!!!!!哈哈哈哈哈哈...... * * 无耻啊,无耻!无赖啊,无赖! * * 这到底是跨国公司还跨国无赖?你这个毫无廉耻毫无信用不择手段赖帐的美国杜邦! * 敬请各位人士为拙词谱曲,自吟自唱,抑制住自己的强烈恶心,仔细欣赏美国杜邦披着跨国公司的漂亮外衣,干着极其强横无耻的跨国赖帐勾当! |
From: Juan R L. <mes...@ve...> - 2006-07-17 13:51:46
|
I recently installed Ubuntu onto a Power Mac G4 and was wondering if Ndiswrapper is benificial to my system.I have an Aiport Extreme card installed and connect via DSL through my Apple Airport Station when under OS X (I dual boot).I have yet to be able to connect under Ubuntu and have heard much talk abouit your product. Would your software be compatible with my Mac's hardware? Sincerely, Juan |
From: Dominique R. <do...@le...> - 2006-07-17 14:02:47
|
Le Mon, Jul 17, 2006 at 08:51:16AM -0500, Juan R Leon [meshica7@verizon.n= et] a =E9crit: > I recently installed Ubuntu onto a Power Mac G4 and was wondering if > Ndiswrapper is benificial to my system.I have an Aiport Extreme card > installed and connect via DSL through my Apple Airport Station when > under OS X (I dual boot).I have yet to be able to connect under Ubuntu > and have heard much talk abouit your product. > Would your software be compatible with my Mac's hardware? Ndiswrapper can only use Windows drivers on x86 and x86_64 platforms, so it won't be o any use for you with Macos on PPC. btw, since recent kernel versions have native broadcom implementation, you should be able to get something to work : http://forums.gentoo.org/viewtopic-t-409194.html (it wil require some knowledge of linux kernel compilation) Dominique --=20 Dominique Rousseau Si cinquante millions de gens disent une sottise, =E7a n'en reste pas moins une sottise. -- Anatole France |
From: Thomas B. <ber...@fr...> - 2006-12-17 11:59:52
|
From: munguanaweza <mun...@hi...> - 2007-01-25 03:32:10
|
Hello Mr. Schild, What dev-tools do I need to install to get my ndiswrapper to make = install properly? I am new with Linux and you will have to specify = which ones that I need. Thanks Hallo Herr Schild, Was fuer dev-tools muss ich installieren? Ich bin Linux anfanger, und = Sie muessen die was ich brauche unterschreiben. Danke |
From: James S. <Sha...@ea...> - 2007-01-25 04:16:36
|
> What dev-tools do I need to install to get > my ndiswrapper to make install properly? > I am new with Linux and you will have to > specify which ones that I need. It looks like you need "libc6-dev" if you're using debian. Your distro may differ. At least for those first couple errors, you need libc6-dev. And maybe some others depending on what you have/don't have on your system. - James |
From: Pavel R. <pr...@gn...> - 2007-01-25 06:36:28
|
On Wed, 2007-01-24 at 22:16 -0600, James Shatto wrote: > > What dev-tools do I need to install to get > > my ndiswrapper to make install properly? > > I am new with Linux and you will have to > > specify which ones that I need. > > It looks like you need "libc6-dev" if you're using debian. Your > distro may differ. At least for those first couple errors, you need > libc6-dev. And maybe some others depending on what you have/don't > have on your system. No, the original poster mentioned a site about SUSE in a separate thread, so that would be glibc-devel. munguanaweza, please use "reply" instead of starting a new thread. This way, your previous messages about the topic will be easier to find. Also please post in plain text without HTML. And if you are using an unofficial documentation rather than the one that comes with the driver, it would be better to contact the author of that documentation, who could fix it for the benefit of other users. -- Regards, Pavel Roskin |
From: Giridhar P. <pg...@ya...> - 2011-12-31 20:39:36
|
Stable version 1.57 has been released (took lot longer than expected, as Pavel Roskin kept fixing it!). Following is short summary of changes: * Added support for Linux 2.6.35 - Linux 3.1 * Kernels as old as 2.6.14 are now supported * IW_AUTH_MFP implemented * Reserve stack before copying arguments when calling from Windows to Linux on x86_64 * Fixed a kernel panic if there are many devices for one driver and one fails to initialize * Fixed a kernel panic with Marvell USB if ndiswrapper is reloaded * Fixed support for AVM Fritz USB * Loading drivers with unknown symbols is disallowed, it's a certain crash * Fixed procfs registration if the network device is renamed * Added more function stubs * Build system improved * Code cleanup, fixed many warnings, style issues and typos Giri |
From: boywhp w <bo...@gm...> - 2012-01-01 01:26:50
|
good job!!! > Stable version 1.57 has been released (took lot longer than expected, as > Pavel Roskin kept fixing it!). Following is short summary of changes: > > * Added support for Linux 2.6.35 - Linux 3.1 > * Kernels as old as 2.6.14 are now supported > * IW_AUTH_MFP implemented > * Reserve stack before copying arguments when calling from Windows to Linux > on x86_64 > * Fixed a kernel panic if there are many devices for one driver and one > fails to initialize > * Fixed a kernel panic with Marvell USB if ndiswrapper is reloaded > * Fixed support for AVM Fritz USB > * Loading drivers with unknown symbols is disallowed, it's a certain crash > * Fixed procfs registration if the network device is renamed > * Added more function stubs > * Build system improved > * Code cleanup, fixed many warnings, style issues and typos > > Giri > > > ------------------------------------------------------------------------------ > Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex > infrastructure or vast IT resources to deliver seamless, secure access to > virtual desktops. With this all-in-one solution, easily deploy virtual > desktops for less than the cost of PCs and save 60% on VDI infrastructure > costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox > _______________________________________________ > Ndiswrapper-general mailing list > Ndi...@li... > https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general > > |