Let me say: I fixed in PicoXP, using the functionality offerred by WinBuilder 82.
I fixed it a little bit more universal (no hardcoded Expand like you suggested).
Spoiler
CopyOrExpand,%source_win%\AUTOEXEC.NT_,%target_sys%
If,ExistFile,%target_sys%\AUTOEXEC.NT_,Begin
FileDelete,%target_sys%\AUTOEXEC.NT_,NOWARN
Expand,%source_win%\AUTOEXEC.NT_,%target_sys%
End
CopyOrExpand,%source_win%\CONFIG.NT_,%target_sys%
If,ExistFile,%target_sys%\CONFIG.NT_,Begin
FileDelete,%target_sys%\CONFIG.NT_,NOWARN
Expand,%source_win%\CONFIG.NT_,%target_sys%
End
You are right: It looks like a WinBuilder bug, and w/o looking into the source code, IMO it is a WinBuilder bug .
But it does not help anybody, when I fix in my private WB 83, and WinBuilder is frozen on 82.
Location:The Outside of the Asylum (gate is closed)
Italy
Posted 23 March 2013 - 07:41 PM
Let me say: I fixed in PicoXP, using the functionality offerred by WinBuilder 82.
I fixed it a little bit more universal (no hardcoded Expand like you suggested).
I am not sure to understand (actually I am sure I don't understand) .
CopyOrExpand,%source_win%\AUTOEXEC.NT_,%target_sys% If,ExistFile,%target_sys%\AUTOEXEC.NT_,Begin FileDelete,%target_sys%\AUTOEXEC.NT_,NOWARN Expand,%source_win%\AUTOEXEC.NT_,%target_sys% End
CopyOrExpand,%source_win%\CONFIG.NT_,%target_sys% If,ExistFile,%target_sys%\CONFIG.NT_,Begin FileDelete,%target_sys%\CONFIG.NT_,NOWARN Expand,%source_win%\CONFIG.NT_,%target_sys% End
You are right: It looks like a WinBuilder bug, and w/o looking into the source code, IMO it is a WinBuilder bug .
Yes, but I wonder what could be the cause, most probably the issue is the extension of the compressed file being three chars and ending with the underscore BUT the uncompressed file having an extension only two chars long. Nasty.
But it does not help anybody, when I fix in my private WB 83, and WinBuilder is frozen on 82.
Well, it doesn't help anyone NOW, but it might help someone "tomorrow" .
I'm sure that after that you fully understand my code.
If not, a brief explanation:
The "standard" command is CopyOrExpand.
If it does not work correctly by any (propably WinBuilder bug) reason, the target contains the file from source rather then the expanded source.. In this case
delete the copied file in the target
explicitelly "Expand" the source file into the target.
The CopyOrExpand method is necessary, because in several different source CDs files are sometimes stored compressed as ???.??_ file, and sometiimes uncompressed as ???.??? file. That's design by Billy the Door.
Location:The Outside of the Asylum (gate is closed)
Italy
Posted 24 March 2013 - 08:58 AM
Yep , it is not that difficult to understand, notwithstanding the commas .
The CopyOrExpand method is necessary, because in several different source CDs files are sometimes stored compressed as ???.??_ file, and sometiimes uncompressed as ???.??? file. That's design by Billy the Door.
That's the piece of information I was missing , never noticed such a source with "already expanded" AUTOEXEC.NT and CONFIG.NT .
Location:The Outside of the Asylum (gate is closed)
Italy
Posted 27 April 2015 - 04:10 PM
Thank for Peter and Wonko.
I used PicoXP boot from CD in VMware ,and virtual machine have C: D:
But I can not find C: D: .It seemed that PicoXP can not load File System?
And I can't understand what Wonko mean?
Thanks!
VMWare can use a (virtual) hardware which is NOT always by default seen in a XP or in any "basic" PE, because a driver for that (peculiar) hardware is missing and needs to be added to the build.
Please note that the needed driver depends on the kind of device you use in your VmWare Virtual MAchine, there are two possibilities, the IDE disk or the SCSI disk.
Make SURE that your VM is using a IDE disk and NOT a SCSI one.
1) try again VmWare after making sure that you are using a IDE disk as (hopefully) the "Standard Dual Channel IDE Controller" driver will work on it
2) use another Virtual Machine (like Qemu) that uses only a "plain" (virtual) IDE adapter which surely works with the "Standard Dual Channel IDE Controller" driver
3) add to the PicoXP the needed driver for the "special" (virtual) hardware VmWare uses when using a SCSI disk (LSI Logic)
I came across this project for winbuilder and bow my head at the nice implementation. I was wondering if there is a way to have a COM port work in PicoXP.
My goal is to run a 16-bit program in a virtual machine that communicates via COM port. I get the program to work but it doesn't see any COM port. Unfortunately I wasn't able to find anything on how to add a COM ports to PicoXP. Any tips or pointers to other projects would be greatly appreciated.
thanks for your quick response and the new script. I tried your script and initially I got an error for a missing file UMPNPMGR.DLL when running the built ISO. I have set the BIOS of the VM to have both COM ports on AUTO, so at least one should show up.
I added UMPNPMGR.DL_ to your script so that UMPNPMGR.DLL is expanded to i386/system32 and the error goes away. However, I still don't see a serial port. I use NT_TTY.exe and it's setup dialog to see if I have any available COM ports but it none shows up. Not sure where to go from here. Any more pointers would be greatly appreciated.
Location:The Outside of the Asylum (gate is closed)
Italy
Posted 17 November 2015 - 08:02 PM
I'm a bit confused. Your link points to a topic having three other links. Two of them have nothing to do with devcon.exe The third one tells me that the contents is not open. I have to register or login.
Peter
On this thread: http://www.msfn.org/...mation-package/ a user mentioned the news that MS Open Souced devcon.exe providing a link to the code.msdn page where the source was released. Then upon request, here: http://www.msfn.org/...kage/?p=1091396 he attached a redistributable version (compiled by him making use of the MS Open Source released code). This link: https://code.msdn.mi...Sample-4e95d71c iswas at the time the actual code.msdn home page for devcon (source and license). As usual the good MS guys spend half of their time ruining Windows NT and the other half moving things around so that they canno be found anymore.
They are currently in the process of moving all their Open Source stuff to Github (of course without leaving coneections to the new place on the old server).
This license governs use of the accompanying software. If you use the software, you accept this license. If you do not accept the license, do not use the software.
1. Definitions The terms "reproduce," "reproduction," "derivative works," and "distribution" have the same meaning here as under U.S. copyright law. A "contribution" is the original software, or any additions or changes to the software. A "contributor" is any person that distributes its contribution under this license. "Licensed patents" are a contributor's patent claims that read directly on its contribution.
2. Grant of Rights (A) Copyright Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, each contributor grants you a non-exclusive, worldwide, royalty-free copyright license to reproduce its contribution, prepare derivative works of its contribution, and distribute its contribution or any derivative works that you create. (B ) Patent Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, each contributor grants you a non-exclusive, worldwide, royalty-free license under its licensed patents to make, have made, use, sell, offer for sale, import, and/or otherwise dispose of its contribution in the software or derivative works of the contribution in the software.