Tripredacus

Name has been changed.

Welcome to the MSFN!

Same to you as I posted above: https://msfn.org/board/topic/71610-you-want-to-change-your-username/?do=findComment&comment=1262866

In this forum you must post in English.

I have been using CrystalDiskInfo as a general disk testing tool and have found a couple disks that don't show power on hours info. It shows a dash symbol or is blank. At about what hour mark do the two 2 TB disks reset their time at?

Still a problem.

NTLDR is missing message comes from the OS itself, so this means it can see the disk. This message means that the BIOS did the hand-off to the disk, read the boot .ini and found where the OS is, but the path did not resolve. So the first thing to do is to check the boot .ini and see what is in there. One example of a situation where a BIOS update can cause this is if the OS volume where Windows is located had its drive letter change. Such as if you are using multiple hard disk and Windows is in D: a BIOS change could cause the re-enumeration of volumes and D: is now E:, etc. If it is a situation where your OS was on C: but now that volume is a different letter, then it may be better off reverting that BIOS version again as the Windows installation could have problems with the drive letter changing. NOTE: The forum will not let you type in the term I put in bold above without a space. You will get an error if you try to submit a post without the space. EDIT: I'd also like to report that while the retroweb (site linked earlier) is good for information, I find their software to be lacking. That site does not take into account board revisions such as is common with Microstar boards which means this issue will likely exist for other brands. That would be a reason why a BIOS update may fail. Also I've yet to find any drivers on there that have worked. For example, ones that are marked for Windows 95 requiring different OS like XP, or 32bit options are 64bit versions, etc.

In case anyone has trouble reading through this thread, I can provide this bit of information. Using Dell Optiplex 9020, the LAN HwID is VEN_8086&DEV_153A The driver located in ProEMbSw11.exe in the PRO1000\WinXP Related\PCIe works just using manual update through Device Manager without having to do any file modification. Fortunately, it appears this file is in Archive from when it used to exist on Intel's website: https://web.archive.org/web/20181201110458/http://downloadmirror.intel.com/22928/eng/PROEmbSw11.exe

I have no idea if Google sells the information or not. Are these new people to the internet? Likely their data is already sold. Personally, if it was a small bit of information, I wouldn't use a form or a database. Just send the information and store it manually on your local system. If the information is not supposed to be shared to everyone, there is no reason to host the data on a server.

*taps the sign It is the same as previous OS, the issue is the Shell, not the OS.

Topic title changed, see rule 12. If the title is wrong, you can edit it to be what you want it to say.

Russia is blocked because of spammers. Nothing wrong with Russian people posting here, if they are breaking a law in their own country then that is something they will have to deal with themselves.

Name changed

On the host system (where the share is located), you create a user account with password. Then you use that username/password on the remote system... For example, Computer2 is the server (the location of the share), Computer1 is the client. You create an account on Computer2 called Account2. On the client, you connect to the share and the username you use is Computer2\Account2. If you only type Account2, the client will "send" Computer1\Account2 and if the server does not know what Computer1 is, then it will reject the credentials. Alternatively, I believe that you can add accounts from other computers to share permissions, but I don't remember if a password is required. To do that, you would add Computer1\Account1 on the server side and it will recognize that user. I don't remember if adding that to the share/permissions is enough or if you have to add it to Users as well.

The CD Drive that gave me the error had been used with this OS for over 20 years now, so it isn't like it is some brand that wasn't compatible. But this computer has sat being unused for a very long time and if the CD drive was the only thing that failed in that period I should count myself fortunate. I can see it being picky about the USB CD drive, which is known working on other systems. It turns out I have about 30 IDE ODDs at home so hopefully one of them will work. This computer uses Win 98 FE just because that was the newest OS that was available at the time it was installed. Perhaps it may have been technically true that SE had come out by then, but that was back when I was a farmer and didn't have a wider access to software once I later entered the computing industry. I never needed to update it because everything worked and my next computer ran XP so I didn't have any issues with compatibility.