Recommended Posts

  R-Style said:

If you have a look at that properly, you will see that it's a device driver that lets you access NTFS partitions under Win98, but it also clearly states that you cannot have the boot partition of Win98 on an NTFS partition...

Recommended Configuration

Do not convert your first partition, or your Windows 95/98 boot partition (the one with \windows on it), to NTFS as there is no support in Windows 95 or Windows 98 for reading NTFS drives during the boot sequence.

For maximum compatibility in dual boot systems, the recommended partition configuration is to maintain a FAT partition as the first partition on the primary drive. This partition should contain Windows 95/98 and should not be used to store applications or data files. The rest of the primary disks, and any other disks that you wish to share between Windows 98 and Windows NT/2000/XP can be formatted with NTFS or other file system types (FAT16 or FAT32) that are understood by the operating systems from which you wish to access them. Your Windows NT/2000/XP system directory can be placed on either a FAT or NTFS drive (note that Windows NT 4.0 cannot be placed on a FAT32 drive, nor boot from a FAT32 drive).

Below is a file system compatibility chart that can help you determine which file systems to use for compatibility in your dual boot environment.

Therfore it does not allow you to install and run Windows 98 on an NTFS partiton, you can merely access an NTFS partition on a system that is running Windows 98 on a FAT or FAT32 partition.

first of all i have never seen windows 98 ever being able to read an NTFS partition and even if it did, NTFS is usefull only for securing data. As users in 98 are not differentiate in win98 as in win2k or winxp, the security concept goes down the drain. (different users cannot access each others data on an NTFS partition

)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • It seems like I'm just renting games now. I can't resell them and they can be removed from the steam or Epic store or the servers shut down at any time.
    • Sure - let's expand on that a bit then to try and be of more help. It's not a one-time use code that can be gamed - each time the proof is required a new transaction takes place to go through the "proof" process. It's a unique step each time. Not a...reusable QR code or pass so to speak. Each time proof is required, a new cryptographic transaction is required. The tricky part here, is trusted issuers. That is still needed. Since this is open source - it doe snot mean that Google has to be the issuer. Google has just provided the tooling to do this, but they don't store the data - to be clear. Presumably, again - you would have some type of government or state issued digital ID that supports the zero-knowledge functions. Effectively, the same entities today that have your information and you (assumingly trust) would continue to have it, it would just be able to be leveraged in a more private manner when you go somewhere or interact with anything requireing age verification. To fake this, someone would need to have a legitimate private key tied to an actual real identity. Cryptographic checks using zero-knowledge would fail otherwise - and again - it can't be used over and over again. Can someone screw up and somehow leak that private key? Sure. No different than leaking your password to your private accounts - a password change would be necessary and let's hope that future implementation of ZKP-based identities bake in some kind of 2FA/MFA for better security. There's not much to hack here, as I said - really comes down to the issuer. If you receive this from the government, none of your real data gets sent to say "MyHubOfChoice.com" when doing age verification - the protocol is only designed to say "Yes - I meet the requirement." Reality is, this keeps you more anonymous than you could ever be today with age verification without having to share anything else about you. However, it's worth stating that anonymity isn't the goal with ZKP - it's removing disclosure. True anonymity is more difficult, as how everything works today to an extent you need to prove who you are with a "trusted" source (ie government/state issued ID). And that data, at the end of the day, does sit in a centralized db as designed. Could that change in the future, perhaps. But the goal of this is just to not have to hand over anymore information than you need to.
    • Oh yeah because its SO hard to duplicate some of the server's logic on the client
    • Software versions increase while older ones are deprecated. This is nothing new, except now it's not included with Windows. Do you not upgrade your software? The biggest issue for me living with 2.0 was that the new versions never upgraded it, it installed side-by-side. I accidentally launched the shite version more than once on accident.
    • They would have to include .NET (not be to be confused with legacy .NET Framework), and they don't. That might be why...dunno. Or maybe because it's open source (guessing)? It's kind of nice to have it separated from the OS.
  • Recent Achievements

    • One Year In
      K.I.S.S. earned a badge
      One Year In
    • Week One Done
      solidox earned a badge
      Week One Done
    • Dedicated
      solidox earned a badge
      Dedicated
    • Week One Done
      Devesh Beri earned a badge
      Week One Done
    • Week One Done
      956400 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      444
    2. 2
      ATLien_0
      162
    3. 3
      +FloatingFatMan
      147
    4. 4
      Nick H.
      66
    5. 5
      +thexfile
      61
  • Tell a friend

    Love Neowin? Tell a friend!