Computer name problem

Topic

New Reply

After reinstalling XP Home on my friend’s old laptop I wanted to change the computer name to Maria’s Old Laptop but was told that couldn’t be done as the name included unacceptable characters, presumably referring to the apostrophe. I then changed it to Marias Old Laptop but got the same message, and can’t understand what characters are unacceptable in that name, and why do Microsoft impose such a rule anyway.

Can someone please enlighten me as to what is wrong with the name?

Thanks and regards,
Roy

Reply | Quote

Replies

Just a thought, are spaces allowed in the computer name?

Reply | Quote

Roy,

Maybe this article will help? :cheers:

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

Reply | Quote

Windows doesn’t like spaces in a computer name: Computer names can’t … contain spaces.

Bruce

Reply | Quote

After reinstalling XP Home on my friend’s old laptop I wanted to change the computer name to Maria’s Old Laptop but was told that couldn’t be done as the name included unacceptable characters, presumably referring to the apostrophe. I then changed it to Marias Old Laptop but got the same message, and can’t understand what characters are unacceptable in that name, and why do Microsoft impose such a rule anyway.

Can someone please enlighten me as to what is wrong with the name?

Thanks and regards,
Roy

That’s one reason, that some history with computers is advantageous.
Like, Forever, a disk drive can have only eleven characters in its name and NO spaces or special Characters.

“MariaLaptop” would work. Your example WILL NOT!

For safety, when naming any Windows folder, always stay with the old DOS rule, “no file or folder name shall exceed 8 characters”.
Life will be a lot easier if you just follow a few simple rules of computing.

I can’t quote the exact rule, but when burning data files to DVD’s, the burners, like NERO, don’t like to see nested folders….one folder under another folder, under another folder, under another, etc., etc, etc.

Good Luck!
The Doctor

Reply | Quote

when burning data files to DVD’s, the burners, like NERO, don’t like to see nested folders….one folder under another folder, under another folder, under another, etc., etc, etc.

That’s related to the maximum number of characters in a path string. The entire file name and directory structure has to be under 256 characters to meet older recordable media standards. Newer computers can handle much longer paths but if you want it backwardly compatible, its another rule like dir names. For backup purposes, it’s yet another reason to keep directory names modest. They may be fine in Windows but if you have to restore them from a command line…

Reply | Quote

You can add dashes to get separation, maybe underline as well, but, then you always have to remember those characters are part of the computer name as well.

Reply | Quote

Another thing that doesn’t like spaces in the name is your wifi SSID. Some wireless devices won’t be able to connect to your wifi if you have spaces in the SSID.

But that’s another subject.

Group "L" (Linux Mint)
with Windows 10 running in a remote session on my file server

Reply | Quote

Another thing that doesn’t like spaces in the name is your wifi SSID. Some wireless devices won’t be able to connect to your wifi if you have spaces in the SSID. But that’s another subject.

Indeed it is, but you’ve raised it. I’ve seen many SSIDs with spaces in. In fact my one is called Go Away! …

BATcher

Plethora means a lot to me.

Reply | Quote

SSID … In fact my one is called Go Away! …

My cellphone’s WiFi SSID also has spaces in it, “Whoomp! (There It Is)”, and it seems to work fine.

Reply | Quote

What was your solution?

You’ve gave thanks to a few replies, which one worked?

Reply | Quote

Mine’s Homeland Security. I went serious instead of HomeLan Security

Reply | Quote

Spaces in the SSID prevent some wireless devices from being able to connect to it. At my church we had a laptop in the soundbooth; no network jack anywhere near it. But no matter what I did, I couldn’t get it to connect wirelessly. However, if I moved it to where there was a wire and plugged in, I got connected without any problem.

The SSID had a space in the name. I renamed it, this time with no space. The laptop immediately connected, and has connected with no problem ever since.

Group "L" (Linux Mint)
with Windows 10 running in a remote session on my file server

Reply | Quote

Browni, getting rid of spaces worked.

Reply | Quote

Browni, getting rid of spaces worked.

Although some devices will connect if there are spaces in the SSID, others won’t. It’s an easy thing to see if that is the problem.

I’m glad you got it working.

Group "L" (Linux Mint)
with Windows 10 running in a remote session on my file server

Reply | Quote

Although some devices will connect if there are spaces in the SSID, others won’t. It’s an easy thing to see if that is the problem.

I’m glad you got it working.

… but SSID wasn’t the topic of this thread.

Bruce

Reply | Quote

Anybody try character 0 as a spacer? To use that press the alt key with 0 on the number pad and release.

Reply | Quote

Best practice is to use underline for spacing. CD/DVD burning with Starburn (freeware burning program) from a 64-bit Toshiba Satellite laptop doesn’t care about nested folders. And SSIDs should not contain spaces. DOS 8-character limits do not apply to modern 64-bit hardware or the media they use. FAT-32 cares about name length, but NTFS does not so much. Any more sub-topics we should clear up here?

-- rc primak

Reply | Quote