Jump to content

Tripredacus

Supervisor
  • Posts

    13,110
  • Joined

  • Last visited

  • Days Won

    24
  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by Tripredacus

  1. 13 hours ago, Cixert said:

    Do you know if there is a way to install ACPI.SYS on a Standard PC installation? (then I would change the HAL files)

    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.

  2. 17 hours ago, Dixel said:

    Chrome 109 from 2022 might be too old. Works fine for me on 119.

    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.

  3. 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.

    1b1DVPF.jpeg

    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.

  4. 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.

  5. 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

  6. 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.

  7. 5 hours ago, MrMateczko said:

    I understand that, I will mention my old nickname in the signature as well as in the About Me page on my profile.

    I confirm that I want to change my nickname as requested.

    EDIT: The avatar will stay so it can be used to identify me as well.

    Name changed

  8. 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.

     

     

  9. 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.

  10. My ASPI memory had to do with Adapter controller cards and not specifically with the CD drives. 

    I tried 2 other drives, one works but it has mechanical problems, so perhaps it is actually the drive and not something else. I tested using a Windows 95 CD-ROM boot disk. I'm out of IDE ODDs here, I'll have to dig through the stockpile at home and see if any of those work.

  11. Windows 98 FE, having issues with CD drives. Same behaviour with both an IDE and USB CD drive. The drives are detected in Device Manager. They get drive letters in My Computer. Both respond to the Eject command, but when trying to access either drives it immediately will say "Device is not ready" without any attempt to read from the drive. I have reinstalled the chipset drivers and there has been no change. USB mass storage drives work fine.

    I can still do the old boot into Safe Mode and remove all of the controllers and drives and reboot/reintall, but besides that is there any other thing I can look at that would effect CD drives in general?

×
×
  • Create New...