Recommended Posts

So, my apologies for the ignorance on the subject...

1) NT is based on Win95? If that is the case, can something that works with Win98se (i.e. a CD-RW drive) work with NT?

2) If that's possible, what CD burning software would work with NT? Again, could something that's compatible with Win98se?

Thanks for the help in advance! :D

~JM

Link to comment
https://www.neowin.net/forum/topic/311378-some-questions-about-nt/
Share on other sites

Okay, so then what would I look for in terms of compatibility if something doesn't specifically say it's made for NT?

585809054[/snapback]

it might work but it might not, what version of NT are you installing?? if its NT4 then maybe but if its 2000 then most likely

You can check if specific hardware is officially suppoted on Microsoft's website:

http://support.microsoft.com/?kbid=131303

EDIT: Odd... it says for NT, but they don't list NT any more... :ermm:

EDIT#2: nevermind. It has been moved to "legacy". Direct link: https://winqual.microsoft.com/download/hcl/NT40xHCL.txt

Edited by markjensen

Windows NT was developed to beat OS/2 and compete with Unix server and workstation systems.

Windows NT has no relation to Windows For Workgroups.

Windows NT was built by several of the original OpenVMS designers. NT employs many VMS design concepts.

NT was designed to bring the following to the Windows platform:

1) A new, non-DOS based platform

2) Unix-style file/folder permissions

3) A clear seperation of kernel space and user space. This improves stability and reliability.

4) NT was built from the ground up for threaded operation.

NT was built to support a variety of architectures (as opposed to just x86 which was all that DOS and Windows 3.x supported).

NT was built to support any number of user-space system implementations, which they call "subsystems." Theses subsystems sit on top of the NT microkernel much like the FreeBSD user space sits atop the Mach microkernel on Apple's OS X.

Examples of supported NT OS subsystems include: Win32, POSIX, OS/2, and Interix/SFU.

Micrsooft built Win32 as a common high-level API that would be supported on both NT and Windows 3.x/9x systems. This allowed developers (to some extent) to be able to write an application for one platform and have it work on the others, even though Win32 is not the native API for NT.

So, my apologies for the ignorance on the subject...

1) NT is based on Win95?

No, it is not. It is more based on OS/2 when it comes to the core OS parts, allthough some user mode programs that shipped with the OS was based on the same or similar apps in Windows 98.

If that is the case, can something that works with Win98se (i.e. a CD-RW drive) work with NT?

It is not the case. Something that works with Windows 98se may work with NT, but please note that NT had a very different driver model than 98se. It is very likely that anything requiring a device driver is going to have issues on NT, and may flat out NOT work. Windows 2000 on the other hand re-adopted the 98-style device driver model, so you have better luck finding a match there.

2) If that's possible, what CD burning software would work with NT? Again, could something that's compatible with Win98se?

I don't know the answer to that one, but you may want to spend some time at Google's site to see if you can find something.

My advice would be to forget about 98se and NT, and get a more modern OS --if cost is an issue then consider Linux or FreeBSD for example....

  • 3 weeks later...
Windows NT was developed to beat OS/2 and compete with Unix server and workstation systems.

Windows NT has no relation to Windows For Workgroups.

Windows NT was built by several of the original OpenVMS designers.  NT employs many VMS design concepts. 

NT was designed to bring the following to the Windows platform:

1) A new, non-DOS based platform

2) Unix-style file/folder permissions

3) A clear seperation of kernel space and user space.  This improves stability and reliability.

4) NT was built from the ground up for threaded operation.

NT was built to support a variety of architectures (as opposed to just x86 which was all that DOS and Windows 3.x supported). 

NT was built to support any number of user-space system implementations, which they call "subsystems."  Theses subsystems sit on top of the NT microkernel much like the FreeBSD user space sits atop the Mach microkernel on Apple's OS X.

Examples of supported NT OS subsystems include: Win32, POSIX, OS/2, and Interix/SFU.

Micrsooft built Win32 as a common high-level API that would be supported on both NT and Windows 3.x/9x systems.  This allowed developers (to some extent) to be able to write an application for one platform and have it work on the others, even though Win32 is not the native API for NT.

585810443[/snapback]

Finally!! Someone who knows what they're talking about! :D

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

    • No registered users viewing this page.
  • Posts

    • Because Chrome is doing it. And no one said anyone had to update immediately. That's silly. They could update every day for all I care as long as it's fast, and the next time the browser restarts, you're good. And the basic point is not to tee it up for bigger updates. As it is right now, all the windows I had open reopen anyway except inprivate.
    • Why? Does anybody actually want this? The constant need to close all browser sessions and wait for a new version to install, just so that there’s a integrated coupon manager feels like a waste of everyone’s time
    • I remember when Louis used to just do interesting Mac/iPhone repairs, now he's boring and just launches "crusades" every week
    • A shame it don't allow people to bypass the MS account, I will stick to using Rufus.
    • Microsoft about to radically change how often your Edge browser updates by Paul Hill Microsoft has just announced that starting with Edge 152, it will be moving to a two-week release cycle for faster, smaller updates. This faster release cadence will begin on August 27. This change comes just several months after Microsoft switched Visual Studio Code to weekly updates. The company said that the Extended Stable releases will remain on an eight-week cycle and that no admin changes are needed to experience the faster release cycle on the Stable channel. The new two-week release cycle will enable the faster delivery of security updates and platform improvements, all while reducing the size and complexity of individual updates. Microsoft claims that organizations will benefit from this change as it offers predictable validation cycles. For organizations that prefer a “more deliberate pace”, the Extended Stable channel remains an option. This change will affect Edge Stable releases on Windows, macOS, Linux, and mobile. The Extended Stable channel will continue to be updated every eight weeks, or every fourth Stable release, for example: versions 152, 156, 160, and 164. The Extended Stable could be a good option for organizations that don’t want the latest updates twice a month and don’t want as much hassle constantly updating browsers. In the case of Visual Studio Code, many of the updates being pushed by Microsoft are AI-related. As we all know, Microsoft Edge has a lot of AI features, so we could see Microsoft pushing more AI, thanks to the faster cycles. On the flip side, quicker releases could mean faster security updates, which is beneficial in a world where AI systems are hunting for software exploits. What do you think? Let us know in the comments. For more updates on Edge, be sure to follow Neowin's coverage. In May alone, we reported on Edge offering in-browser pop-ups to assist users with website compatibility issues, that Edge was losing Copilot Mode, and that Microsoft had fixed a plain-text password bug in Edge. Source: Microsoft 365 Admin Center
  • Recent Achievements

    • Week One Done
      davidbazooked earned a badge
      Week One Done
    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
  • Popular Contributors

    1. 1
      +primortal
      514
    2. 2
      PsYcHoKiLLa
      185
    3. 3
      +Edouard
      159
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!