running assemblers and compilers (old dos stuff 32 bit) some of them need to create temporary files for work spaces. the ones that don't run perfectly and this system is great to use. The output files go to where that are supposed to go into the source folder
Temporary DOS files are no different from other files. DOS API provides for a function returning a random file name. Your programs will use that. Composing that name, early vDos versions used an example code fragment published on the Internet. That however didn’t create an actually random name. Moreover, the same code was also used by a virus program.
So I guess you use an old vDos version and your antivirus program blocks creation of that suspect file name.
I downloaded it today and after we talked i down loaded another copy which is identical. what i download has nothing like the software rev level in the .exe properties file version in both cases its 0.0.0.0.
I ran the process monitor the C:\vDos stuff spawns nothing, this would suggest whatever the problem is seems internal to vDos's own task identity and the space it grabs and the way it divvies it up.
maybe you need something like Memmaker or the like or some internal diagnostic or tracer but MEM shows 576K,160K,8192K XMS
The assemblers that work are creating big files without trouble so there is something special about the temporary its trying to create on the C code compiled ones that need a big workspace
ABOUT at the command prompt gives me no rev level just looks like a JPG of boiler plate text on history containing no numbers.
I get no EMS, the XMS is last in what i get I'm using win 7 Home premium. 64 bit with 8gb Ram. Its is normally my CAD system for computer musical instrument parts
I'm a bit confused about what i get using Process Monitor it looks like vDos is a totally self contained task with its own file system and the files in this system are internal so Process Monitor notices nothing. Maybe i need some pointers on getting it to spit out vDos file happenings because the connection between vDos and the windows path still seems real time and maybe i'm looking at the wrong stuff for file activity
just deleted everything, download a fresh copy off your site using this last link you sent. installed it and it's the same
attached jpg is from the first screen it comes up with that produces a command line, which i typed 'about' into.
this is amazing i've downloaded over the last 3 days it seems three files that seem to be identical each 2,318Kb in size
and they all appear to be wrong.
Is there something I've missed here, is there a hidden download/upgrade after installation that is not taking place.
My end use is to create software development systems for older style non RISC MPU chips that are now being used here to train students on assembler programming ease offered by CICS architectures that had complex i/o features. Lots of stuff is being archived using older CPUs people want these to be working archives and are prepared to pay for the tools they need.
My test bed is using the Motorola families like the MC68HC11, there are about 30 CPUs i need to address
That “vDos-Base…” in ABOUT gave away what’s going on.
vDos-Base is the last fully opensource version of vDos. That gets first installed, then patched to the 2021.05.01 version. Previous installation programs had an option to skip the patch. But that caused confusion, so it’s now done ‘behind the scenes’. For some reason it seems the patch isn’t performed on your system. So you end up with vDos-Base.
I’ll send you the vDos 2021.05.01 executable by wetransfer.
it is running now what do i need to do to get the windows C:\vDos folder back to get files in and out from windows I was just dropping a folder full of files into the windows porthole and they emerged in the dos world. And after running dos stuff I could get the results in windows. This was the main attraction