#WINDOWS 3.1 DOSBOX INSTALL#
#WINDOWS 3.1 DOSBOX DRIVERS#
#WINDOWS 3.1 DOSBOX ARCHIVE#
#WINDOWS 3.1 DOSBOX CODE#
#WINDOWS 3.1 DOSBOX WINDOWS 7#

Create a folder called 'Drive C' (Just like the Drive A folder, it doesn't have to be that exact name) and then copy the WININST.BAT file from the 'Drive A' folder to the new 'Drive C' folder. On Windows, MacOS and most distributions of Linux you just have to double click the img file and it will mount it as a drive, you can then copy the files from the mounted drive. Now you have to extract the contents from all of the img files and copy it into the same 'Drive A' folder using your disk image mounter. Create a folder anywhere on your computer named 'Drive A' (It doesn't have to be that exact name, but make sure you know that it is the drive letter A). Make sure to read any readme file that comes with it. You can also extract the other files that came with it, however, that is optional.

#WINDOWS 3.1 DOSBOX ARCHIVE#

img files from the archive using your preferred archive manager, the files should be labelled: disk01.img, disk02.img, disk03.img and disk04.img, this may differ depending where you downloaded from, but it should be similar to these ones listed here. This example uses the files from WinWorld. This may vary depending on where you originally downloaded the disks from, however, the method should work on most sources. img files)ДЄn archive manager (If you download the disks from WinWorld, you need an archive manager that supports 7z files, such as 7-Zip or WinRAR)Д®xtracting the disk image files and setting up the files for use:

DOSBox installed and running on your machineДЄ copy of all four Windows 1.0 Alpha installation disks (Can be retrieved from WinWorld or from here if you have access to the BetaArchive FTP)ДЄ disk image mounter or viewer (Usually already a feature of the OS, if it isn't you can search online for some disk image mounting tools that work on your OS.

#WINDOWS 3.1 DOSBOX INSTALL#

To install Windows 1.0 Alpha you will need: I would try to log INT 21h and INT 2Fh calls in DOS Box.This applies DOSBox running on the following OSes: Click the Display box, scroll down to the bottom, and select Other display (Requires disk from OEM). Click the Options menu in the Windows Setup window and select Change System Settings. I am trying to work out how the lock / unlock file test is done so I can try to remediate within DosBox and create my own test program to replicate in C or VB In Windows 3.1, double-click the Main program folder and double-click the Windows Setup icon. I don't know it for sure, but I would assume that it intercepts DOS interrupts and uses Win32 API calls to simulate needed behavior. I suspect NTVDM.exe is translating it somehow I'm not sure if LockFile existed in Win16 (probably not), but there is possibility that sharing API is called directly through DOS interrupts. However within the VB.exe I can't find any reference to LOCKFILE API

#WINDOWS 3.1 DOSBOX CODE#

Looking at vDos source code could help if you plan to bring this funcionality to Dos Box You could also check 5dh functions marked mostly as internal. This function unlocks access to a region of the file which was previously locked. The region of the file that begins at file logical offset CX:DX extending for a length of SI:DI is locked. This function locks access to a region of the file identified by the file handle in BX.

Returns: AX error code if CF is set to CY SI:DI length in bytes of region to lock (SI * 65536)+DI In 0x21 interrupt code 0x5c handles locking and unlocking filesД¬X:DX file offset from start of file (CX * 65536)+DX SHARE.EXE intercepts DOS Interupt (0x21) and DOS Multiplex Interrupt (0x2F). It must be run, to hook into system and intercept some requests. SHARE.EXE works as Terminate and Stay Resident kind of program. I am trying to work out how the lock / unlock file test is done so I can try to remediate within DosBox and create my own test program to replicate in C or VB. The APIs that seem potentially related in the import table of VB.exe are: However within the VB.exe I can't find any reference to LOCKFILE API, so I suspect NTVDM.exe is translating it somehow.

#WINDOWS 3.1 DOSBOX WINDOWS 7#

When I set a breakpoint at return of LockFile API and faked a faliure (returned false) On Windows 7 I got the same error message 'SHARE.exe must be installed in order to run Visual Basic'

A Temp file is created with GetTempFilename.

#WINDOWS 3.1 DOSBOX DRIVERS#

This method can also be used to move any drivers or other. Subsequent versions were released between 19 until the series was superseded by Windows 95.

The series began with Windows 3.1, which was first sold during April 1992 as a successor to Windows 3.0. This is only temporary while we complete the file transfer. Windows 3.1x (codenamed Janus) is a series of 16-bit operating systems, produced by Microsoft for use on personal computers. Copy your Windows 95 CD into an easy to find directory such as shown here. Running on Windows 7 32-bit and using a debugger attached to NTVDM.exe I found the following process is used: This method does not require administrative access like the other method, the only tool we are using here is DOSBox itself. Some old MS-DOS applications just check for existence of the EXE and it's presence in autoexec.bat, but in this case the EXE exists, but the error still occurs.

SHARE.exe must be installed in order to run Visual Basic I was trying to run Visual Basic 4 (16-bit) in Windows 3.1 running within DosBox.

Windows 3.1 dosbox