Re: **Accessing an old Dos-Shell .bat/,pif file through XP Pro or Home

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Pavel (Atin90_at_hotmail.com)
Date: 02/23/04 

Date: Mon, 23 Feb 2004 11:29:17 -0800

Not all DOS programs will run under WindowsXP environment. WindowsXP does
not have a true DOS environment so that is the reason. But before you give
up there are few things you can try:

Set the environment in the properties of the PIF to:
Screen....full-screen or window
Compatibility.....Windows95, 256 colors

If the above does not help, consider to have a dual boot for your WindowsXP
that will boot to DOS or Windows98 just for this program.

By the way, what is this program you are trying to run? Maybe it has some
additional requirements such as settings that need to be included in
Config.sys and/or Autoexec.bat. 

-- 
Pavel
"RSMAGI" <rsmagi978@bellsouth.net> wrote in message
news:BCD8E94D-E142-4DE7-BCF4-353C68A37DA0@microsoft.com...
> Pavel,
> Thank you for your reply. I too, was somewhat confused by Squire's
reference. However, before even attempting the shortcut, I was able to "see"
the .bat file that was used on the 3 older computers to launch the program.
If I tried to double-click on that file, that black DOS window briefly
appeared. Then I did exactly as you suggested and entered the DOS shell on
one of the XP machines, maneuvered to the network drive and attempted to
start the program directly from there. Unfortunately, that too failed.  I am
puzzled!
>
> Thanks,
>
> RSMAGI
>
>      ----- Pavel wrote: -----
>
>      PIF file extension refers to the Program Information File that may be
>      associated with a DOS application in the Windows environment. This
file
>      contains information about how the DOS application will run in
Windows.
>
>      The PIF file is equivalent to LNK file. You could do properties on
this PIF
>      file and see what is causing the problem you experiencing. Could be
as
>      simple as setting the compatibility mode to Windows 95. Regardless of
what
>      you do, by pointing to PIF file in order to create shortcut, you are
>      creating a secondary shortcut since the PIF file is also a shortcut.
Instead
>      of creating shortcut to the PIF file, create a shortcut that points
to the
>      executable file that the original PIF file is pointing to.
>
>
>      The 'black window' you see is probably some message from your dos
program
>      telling you of some problem. If you still get this 'black window',
you can
>      simply open DOS session by using the Command prompt from your Start
>      menu/Accessories and execute the program directly from there.
>
>      I do not know what is Squire talking about with the NTFS/FAT32 read
>      compatibility since it has nothing to do with your problem.
>
>      Pavel
>
>      "RSMAGI" <rsmagi978@bellsouth.net> wrote in message
>      news:952BBB3D-D9E5-45B9-9799-ADB621EAB2F7@microsoft.com...
>      > We are in a medical office with "antiquated" equipment. The 3
existing
>      computers run on Win 95 (1) and 98 (2). Our basic practice management
>      software runs on a DOS shell and is set-up on the main computer and
easily
>      accessed on our simple, hub-based, network.
>      > We have now brought in 3 new computers that all run on XP Pro or XP
Home.
>      When plugged into the network, they can see the "main" computer with
our PM
>      software, its drive, folder, etc. But when we attempt to create a
shortcut
>      to the program on any of the new computers, we either get a ".pif
file
>      error," or a less than full black window appears momentarily (which
is how
>      the PM program begins on the 3 old computers), but then, the program
does
>      not load and the black window quickly disappears; too quickly to be
able to
>      read the DOS-style message that appears in that black window.
>      > Any assistance would be greatly appreciated.
>      >> Thank you.
>      >> Steve
>      >

Relevant Pages

  • Re: **Accessing an old Dos-Shell .bat/,pif file through XP Pro or Home
    ... If you could post the contents of this BAT file....I will take a look at it. ... If I tried to double-click on that file, that black DOS window ... Then I did exactly as you suggested and entered the DOS ... PIF file extension refers to the Program Information File ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: **Accessing an old Dos-Shell .bat/,pif file through XP Pro or Home
    ... contains information about how the DOS application will run in Windows. ... The PIF file is equivalent to LNK file. ... creating a secondary shortcut since the PIF file is also a shortcut. ... The 'black window' you see is probably some message from your dos program ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Running DOS applications in a DOS box
    ... Unfortunately all that did was shrink my "full screen" mode to a window. ... Normally my DOS ... shortcut) and then made this full screen. ... >>other XP machines it runs in full screen mode. ...
    (microsoft.public.windowsxp.general)
  • Re: Unable to delete
    ... any files that may be in the folders. ... If there are any files, use the Attrib command to remove any Hidden, System or Read-only attributes that may have been set for them. ... Maybe it's Windows Explorer itself that is blocking the deletion; be sure it is focused on some other folder before you open the "DOS" window. ...
    (microsoft.public.windows.file_system)
  • Re: SNAP and 1920x1200 resolution...
    ... these maneuvers shows that there is nothing fundamentally wrong with the video device or its drivers; rather there must be some sort of configuration problem in the windowed DOS object or a bug in the code that launches windowed DOS and WINOS2 sessions. ... Once the windowed session is working, the DOS settings that can be examined and changed dynamically are still the same as those of the DOS window object. ... My guess would be that the video BIOS starts up the video hardware in a really weird mode. ... It is reenterable allowing several DOS sessions to run simultaneously. ...
    (comp.os.os2.misc)