TaoArcher

ohhhhh You cant change it. Workgroup and Domain are an either-or thing. There shoudl be a workgroup called "Domain" where the XP box shows up.

Quote: funny, cause i design my own "NATIVE" XP skins without "hacking" any .dll files. I've got $10 that says your whole version of XP is "hacked"

Quote: Actually, name resolution is an integral part of the browse list. That's why the WINS box has its own ranking in the browser selection. Also, it is used in DC location and credential validation. Better go back to school. The browser service is only responsible for showing the list of computer names on the nearby network for user display, and it uses NetBIOS to do so. If you had an empty Browse list, but you still had your WINS server setup properly, the network would all fucntion properly. It serves NO purpose but for a *USER* to be able to see a list of what network services are available.....when a user selects a resource off of the browse list, the client PC then tries to resolve the name. This guy was only asking how come his PC didnt show up on the list,....which means name resolution has not even played a part yet. Quote: And the machine names are mapped to network locations by...NAME RESOLUTION. NetBIOS translation also includes machine role, which is a function of LMHOST files, WINS boxes, and NetBIOS broadcasting over the chosen protocol (in this case, probably TCP/IP). Exactly, and since this guy is only explaining that his computer does not show up on the list....the problem only lies in the browser service....if he never saw the PC on the browse list, than his PC never tried to resolve the name now did it? Quote: I don't see how the WinXP box could become the master browser when it is able to "log on" with the PDC (hence my request for validation of the connection). All it has to do is request a browse master, and then (if set to "auto" or "maintain") sync its own list. However, with any servers on the network (especially DCs), that point is moot. Not true, if he has a single, PDC, then the PDC is the Domain master browser, and the WinXP box could concievably be on a different subnet than the server....thus being the newst version of the browse service, and assuming the role of the master browser for that subnet. --------- I'm sorry to say this, and i'm not trying to be mean, but you should setup a home network for come trouble shooting, because its hard to teach that in a class. It sounds to me that you have all the words right, but dont see how they all fit in the puzzle.

Wait lets back up here. A computer showing up in the Workgroup list, has nothing to do with Name Resolution, WINS, DNS, Domains or trusts. I'm assuming here that he cant get the WinXP machine to show up in the NetworkNeighborhood Workgroup list, cause that's how i read it. The network neighborhood is created purely using the browse list. (and possibly the local name cache?). My guess as to what's happening, is that the WindowsXP machine became the Master Browser for the network, and the PDC, being the domain master browser, cannot resolve the name of the WindowsXP box, and therefor cant retreive updated information about what computers should be on the browse list. Though it could be alot of things. Lee_frost - try to access the WindowsXp machine from the PDC and make sure you can.

On the XP box, you should probably disable the "Computer Browser" service. The criteria to become the master browser has alot to do with OS version...a news OS will always win a browser election, even if it's only a work station. now I dont know this to be fact, but it's possible there's some incompatibility with Win95/XP browser functions. At least by disabling the CompBrowser service, you'll know that your NT server will be the master browser. Are all these computers on the same subnet? If not it's possible that the Master Browser has not reported yet to the Domain Master Browser about the new machine on the local subnet.

If you hold the SHIFT key while you close a window, it will open in the same place next time. I'm pretty sure it's SHIFT, might be CTRL

I cant get it to work at all....however the Direct3D support on my Voodoo5 seems to work fine, though you might have aperformance issue with it on a voodoo3

Only think i can think is to try switching the slots that your RAM chips are in. See if that works.

Yes you can just delete it. The boot.ini is simple a file that creates the menu. I'm still not sure exactly how NT/2K retains the boot.ini after a drive format. I think maybe it saves a copy in the master boot record? I've wondered this for a long time actually...if anyone knows how i'd like to know.

Quote: Sort of, however if you are using all IDE devices, that both of the drives in question are on the same chain, moving the pagefile from the system partition/disk will be of little consequence as IDE is not capable of simultaneous reads and writes. Now, if you have a SCSI rig, then this would be highly recommended. Oops, i forget that no everyone uses SCSI! hehe. Actually for my new system i'm building in a few months I'm thinking of going with IDE Raid. Any word on the performance of this?

Ok, first let me just clarify something. The page file is not part of NTFS, its simply part of windows. In fact all versions of windows have "virtual memory" ...but in NT/2k/XP, its in the form of a page file. Now a couple things you need to know about it, and some logical ways to deal with it. - Its best to create the page file on a fresh hard drive with nothing on it, to insure that the entire page file is created in one section of your harddrive (this increases seek times). - It is best in most cases to set your Min and Max sizes for the page file to be the same. This way it creates the page file once, and never grows by itself. This way that contiguous file you created above, will never create a new part on a different section of the harddrive. - Its much better (in most cases) to put the page file on a different drive than your OS is loaded. The reason for this is that when you're using memory, the system is reading and writing to this page file. So....rather than loose the drive performance of a single harddrive reading from both page file, and system/program files at the same time, the page file can be accessed via drive #2, whiles your OS files, and applications can be read/wrote from Drive #1. Does that make sense? - The actual size I use is equal to the amount of RAM i have, which is 512 MB. I find this to work fine for me. If you have less ram, you should probably use 1 1/2x the ram you have (so for 128 MB RAM, make a 384 MB pagefile)

Not on the local machine, no....however you can still access a remotely secured file share by using a common username/password.

IMHO, the Updated SBLive drivers from WindowsUpdate are better than the ones creative made available.

IPX is generally a cop-out for getting your network to work right. hehehe. I would turn off your "Computer Browser" service on the WinXP box to start with. Then reboot and see if the problem goes away. If you're part of a domain, theres a bunch of other things to check too.

Quote: eddie, whats this color-wheel prog you're talking about? sounds interesting.. more info? I think what he means is how WindowBlinds gives you the ability to apply a skin, and then apply a specific color to that skin. So if someone made a nice skin, but it was grey, you can apply a nice purple filter to it....and it changes the color on the fly. So i think what he was saying was he'd just like to be able to alter the color of the Luna sytle.