Re: Netsh can't parse funny interface names
- From: "Mark K Vallevand" <mark.vallevand@xxxxxxxxxx>
- Date: Wed, 4 May 2005 09:49:26 -0500
No. I saw this one, and didn't try it. Both images are using the explorer
shell, so I didn't think it applied. I tried it now, and it made no
difference. In my USB ramdisk image, netsh doesn't like the '=' character
in interface names.
--
Regards.
Mark K Vallevand Mark.Vallevand@xxxxxxxxxx
Beer is living proof that God loves us and wants us to be happy.
- Benjamin Franklin
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.
"Slobodan Brcin (eMVP)" <sbrcin@xxxxxx> wrote in message
news:O3yc7CDUFHA.3544@xxxxxxxxxxxxxxxxxxxxxxx
> Hi Mark,
>
> rundll32 netshell.dll HrRenameConnection
>
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xpehelp/html/xehowNamingNetworkInterfacesOnRun-TimeImage.asp
>
> Regards,
> Slobodan
>
>
> "Mark K Vallevand" <mark.vallevand@xxxxxxxxxx> wrote in message
> news:urpQ7NCUFHA.3436@xxxxxxxxxxxxxxxxxxxxxxx
>>I have two images. One to boot from CF and a much smaller one to boot
>>from USB ramdisk. On the CF image netsh works fine on commands like this:
>> netsh interface ip set address "Odd Name z=z" static 172.26.10.0
>> 255.255.0.0
>> But, on the smaller USB ramdisk image, the same command complains that
>> the name "Odd name z" is not found. Its like it get stuck on the '=' in
>> the name. Remove the '=' from the name and netsh is OK.
>>
>> I've added all the netsh stuff that Microsoft and this group has
>> recommended. Still no luck. I'm suspecting that there is a shell
>> parsing dll or something that is still missing.
>>
>> Any ideas?
>>
>> (Oh, the idea "don't use odd names" is implied.)
>>
>> --
>> Regards.
>> Mark K Vallevand Mark.Vallevand@xxxxxxxxxx
>>
>> Beer is living proof that God loves us and wants us to be happy.
>> - Benjamin Franklin
>>
>>
>> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
>> MATERIAL and is thus for use only by the intended recipient. If you
>> received this in error, please contact the sender and delete the e-mail
>> and its attachments from all computers.
>>
>>
>>
>
>
.
- Follow-Ups:
- References:
- Netsh can't parse funny interface names
- From: Mark K Vallevand
- Re: Netsh can't parse funny interface names
- From: Slobodan Brcin \(eMVP\)
- Netsh can't parse funny interface names
- Prev by Date: Re: AAEON 6892 board
- Next by Date: Re: EVC.EXE - Application Error - The instruction at "0x7c901010"
- Previous by thread: Re: Netsh can't parse funny interface names
- Next by thread: Re: Netsh can't parse funny interface names
- Index(es):
Relevant Pages
|