Skip to content
View in the app

A better way to browse. Learn more.

MSFN

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Suggestion for "16-bit app support"

Featured Replies

Some 16-bit files still remain. They are useless since they say "is not a valid Win32 application." (which it is supposed to) so I don't think any 32-bit program will be using these. They are:

C:\WINDOWS\system32\command.com

C:\WINDOWS\twain.dll

C:\WINDOWS\twunk_16.exe

C:\WINDOWS\system\WINSPOOL.DRV (not sure about this one but if it is safe to delete perhaps the 'system' folder could be deleted since it would be nice for autocompleting in the command-line when typing 'system32'. This was the last file in 'system')

C:\WINDOWS\system.ini

C:\WINDOWS\win.ini

C:\WINDOWS\Fonts\dosapp.FON

C:\WINDOWS\Fonts\EGA80WOA.FON

C:\WINDOWS\Fonts\EGA40WOA.FON

C:\WINDOWS\Fonts\CGA80WOA.FON

C:\WINDOWS\Fonts\CGA40WOA.FON

C:\AUTOEXEC.BAT

C:\CONFIG.SYS

C:\MSDOS.SYS

C:\IO.SYS

Also the following file isn't 16-bit and still works even if it isn't useful to most people, but was removed by nLite:

C:\WINDOWS\diskcopy.com

I was using XP SP2 media, and only remove 16-bit support. Let me know if you need more info..


LMFAO!!!

Honestly, if you get rid of either

C:\CONFIG.SYS

C:\MSDOS.SYS

C:\IO.SYS

C:\WINDOWS\system32\command.com

Windows won't even boot!!

Edit: Also, how are you going to run scripts that use the command prompt if you get rid of it... I know you can't but still!!

Edited by undeadsoldier

  • Author
LMFAO!!!

Honestly, if you get rid of either

C:\CONFIG.SYS

C:\MSDOS.SYS

C:\IO.SYS

C:\WINDOWS\system32\command.com

Windows won't even boot!!

Are you sure about that? I removed them, Windows XP still boots, and those files remain deleted. Those files are only a part of DOS/9x/ME boot process, never do they take any part in NT's boot process.

Command line scripts should use a *.cmd extension, not *.bat.

none of those files are required for windows to run

even if you run the nt virtual machine

I'm not even sure it will use C:\WINDOWS\system32\command.com

the nt command prompt is from cmd.exe and it executes .cmd and .bat scripts

and the files on the root have no purpose at all except that some dos program might search for them , but when the virtual machine starts it looks for c:\%windowsdir%\system32\config.nt and autoexec.nt , the io and msdos.sys are not used and don't have a ntvm equivalent

if you don't use the nt virtual machine (or the dos box , or "16 bit applications") then you don't need any of those files

the config.sys,msdos.sys,autoexec.bat files are 0 byte length files are created by XP

for dos compatibilty

real conf goes to config.nt,autoexec.nt as shodan said

Am I correct in assuming you are posting from another computer then?

command.com is a hang-over from the old Dos/Win9x - it should not be required for any NT-based OS to boot, nor function.

Take care,

James

x

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.