I am trying to figure out when MOVEFILE_DELAY_UNTIL_REBOOT operations are performed in relation to System Start drivers (Start=1) on Windows 10 / Server 2016.
Assume the source and target are on the same volume, so it is a move instead of a copy.
This is what is happening with my System Start minifilter driver on Windows 10. As you know, Windows 10 / Server 2016 now keeps loaded SYS files locked.
c:\windows\system32\drivers\mydriver.sys version 1 is loaded at System Start.
upgrade installer tries to update mydriver.sys to version 2 but file is in use.
upgrade installer schedules a move on reboot for the version 2 file.
Reboot occurs
According to my tests, the system is still trying to load version 1 of mydriver.sys!
System then moves in mydriver.sys version 2.
Is this correct? If so, that raises three questions:
1) How is it moving in version 2 after version 1 is already loaded and running?
2) How is Windows updating its own System Start drivers on Windows 10?
3) Is it required to reboot twice to update System Start drivers via MOVEFILE_DELAY_UNTIL_REBOOT with Windows 10 /Server 2016?
I hope this is clear.
Related
In preparation for moving to a new Macbook Pro, I am trying to find a home for my Intel dependent tasks. One such is the Win 10 system that I run under Parallels. I would like to move it to run under Virtualbox on a PC. I have extracted the .hds file from the .pvm package and renamed it to .hdd and added to VB but when I boot it gives an error: "Unexpected Kernel Mode trap". Based on previous posts related to migrating Win 10 from Parallels to VB, I also tried using the prl_disk_tools command to convert the file to plain first and then add it to VB with the same result. Any help in getting this migrated disk to boot under VB would be greatly appreciated.
I am new to this environment and working through the set up for Phoenix Framework.
I installed Node on Windows before someone recommended switching to LINUX. I need to uninstall it on Windows, but following the typical uninstall process produces:
enter image description here
Microsoft assistant said to leave it (expected to take 5 hours - it has now been over 24).
We're in the process of converting our two FoxPro systems to new technology, but meanwhile we need to upgrade our server and I am trying to find out whether our legacy systems will run there. We'd prefer to go to Windows Server 2019, but using Server 2012 is possible. Our stations are Win 7 or 10 Pro, some 64-bit.
One system is in Visual FoxPro 9 and uses its native DBFs and some DBFs in FPD 2.6 format. Certain graphical and document functions (e.g.: OCR) are performed by calls to LeadTools 12.0. The application also calls Outlook.
The second system is a single-user application in FoxPro for DOS 2.6 run from an .app file. The 32-bit stations run this natively, while the 64-bit stations use the product, vDOS, to allow the 16-bit FPD to run there. The application wants to reside on the server since multiple stations can run it, albeit at different times.
Any help is much appreciated. Thank you!
Will a Visual FoxPro 9 EXE run on those server operating systems? Yes.
Will a Foxpro For DOS or FoxPro for Windows EXE run on those server operating systems? No. Those flavours of FoxPro are 16-bit, and as such would require a 32-bit version of Windows Server, the last of which was Server 2008.
However I suspect you are not running either of these on the server. You have a shared folder on the server with the DBFs in it, and the executables are running on workstations.
So if you have a 64-bit OS on the workstation then you can only run the Visual FoxPro exectuable directly. If you had a 32-bit OS on the workstation, you can run both Visual FoxPro and FoxPro for DOS\Windows executables.
Your question is really 'can I put the DBFs in a shared folder on those server operating systems and access them from client workstations?', and yes you can.
I know this isnt a dev question per se, but is there a timeline on a 5.2 build that can be installed on Win 10?
I think the issue i am seeing is just with the installer so an in place upgrade to Win 10 might work fine, but a clean install fails as it doesnt acknowledge IIS 10 or whatever version comes with Win 10.
Thanks!
Official answer - Windows 10 is not yet supported by the currently available Acumatica ERP installers, however the issue has already been fixed internally (AC-56069 - fixed in 4.20.2262, 5.10.0785, 5.20.1012 and newer). Following workaround can be used in the meantime:
Download the Orca tool to edit the MSI file: http://adriank.org/wp-content/uploads/2015/01/Orca.zip
Open the
MSI file using this tool (might be able to right click on MSI and
open with Orca)
Go to the LaunchCondition table
Drop/delete the IIS version condition (inside MSI, the LaunchCondition entry is IISVERSION >="#7"; system does a string comparison and "10" is
smaller than "7")
Save and close Orca
Run the setup
I can't give you an "official" answer but I can give you a work around.
If you download a utility called LessMSI you can extract the installation files. They will come out in a folder called "SourceDir". Simply take these and replace the files in your default installation folder or run them from another location.
Then you can proceed as normal.
The installer only checks if pre-reqs are installed and then copy's the files to the output location. If you have IIS already setup with dotnet support then the rest will be fine.
I do this frequently if I have to install a site with a specific version in order to upgrade or test a client's snapshot.
I have 4.1,4.2,5.1,5.2 running on my Windows 10 workstation as I type
Moving from XP to Windows 7 with client side.
Running into a couple issues with Sybase 15.
1) "Interactive SQL" - many widgets in ie options are defective or missing
2) When running simple query get Swing/AVT widget exception error.
Anyone ran into or worked thru any issues moving to 7?
Other versions of the Windows app, but not 7. As you may be aware 7 is only slightly more reliable than Vista.
Those messages are classically due to (a) Sybase Client (SybaseCentral; InteractiveSQL, the GUI utilities) all using the Java VM and (b) that not being successfuly installed.
Get the Sybase Client CD, and install again. Do not Customise, use the Default installation options. Watch the progress for errors. Ensure the JVM installation succeeds. You may have to retrieve any missing files from the Windows 7 CD.
Otherwise open a Support Case.