Tripredacus

I don't know what a volume OEM copy means. I have done a repair install using an OEM Recovery CD before, but it has been awhile. I also know some OEMs removed the ability to do repair install.

I really don't pay any attention to what is in browsers and not like some of you guys, so I have no idea what is in Iron vs Chrome. What I can say is that the issue with posting or editing a post that contains links is a different issue but still related to this string issue, that thread is here: https://msfn.org/board/topic/185994-cant-edit-my-first-post-in-thread-error-when-posting-links/ I have noticed that the link preview issue is not 100% the fault of the site or the post editor, as it doesn't happen 100% of the time and not with all browsers. But I feel that issues with this site will always happen as IPB being a modern company is keeping up with the times in terms of browser tech, and the users of this forum are generally not.

I never did try to convert this portion of a system. If it happened to me, I would probably clone the disk, then attempt a repair install.

Updated

0x7b stop error means the mass storage driver is missing.

You can get the text back on Firefox 72 before whatever updated in the forum that broke compatibility, and Iron 109. For the MSFN links, when you paste the link, and the preview comes up, click the black banner that says to show only link. It seems that sometimes the preview option for forum links doesn't work.

OT posts hidden.

I am trying to determine what the best way to accomplish my goal of being able to network a modern device (Roku) as well as a some legacy computers (9x, XP) together but using some rules. I have laid out an example diagram here, and this layout is working correctly at the present time. What I want to accomplish is allow PC 3,4 and Server to see each other but not be able to see the rest of the network especially the internet. The server needs to see PC1 or 2 but not the internet. I have considered that I may need to connect a device between the DECA CHA and the Switch. I may be able to accomplish this using VLANs but I am not sure. I do not know if I need one or more than one device and where it needs to be put in the chain. I know I need a firewall of some sort. Potentially the server can bridge the two networks if need be. I haven't built the server yet. The various network equipment I have at my disposal to use to integrate into this are here, but I am unsure if any of these have the ability to do what I want (I am in the process of researching/testing them now) Cisco 2811 with 4 port HWIC Cisco 2821 (it has T1 ports but we'll pretend those aren't there) Ameri.com S53R24i Allied TeleSyn AT-8324SX CentreCOM 8224XL HP ProCurve 2910al-24G All of the above are 10/100 except the HP which is gigabit. DECA limits out at 54mbps so Fast Ethernet is fine. I also have some 100FX stuff also but that is a project for future me.

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.