Jump to content











Photo
- - - - -

Version 2.0.10


  • Please log in to reply
2 replies to this topic

#1 v77

v77

    Silver Member

  • Team Reboot
  • 569 posts
  •  
    France

Posted 19 November 2018 - 05:47 PM

What is this "cplcore" folder inside the installer? Is that the API without the GUI of the regular imdisk.cpl?

It seems you deleted a more recent version of the readme.txt that we found in the last build of the version 2.0.9. There were mentions of Windows 10...

No compilation for imdisk.sys x64? But I see several small changes in the source...
We can use install.cmd to check the system version and then use a dedicated .inf file to install the version 2.0.9 only for Vista x64 (and by using the .inf file to check the architecture, which is difficult to do in a reliable way in a batch file).



#2 Olof Lagerkvist

Olof Lagerkvist

    Gold Member

  • Developer
  • 1416 posts
  • Location:Borås, Sweden
  •  
    Sweden

Posted 19 November 2018 - 06:13 PM

What is this "cplcore" folder inside the installer? Is that the API without the GUI of the regular imdisk.cpl?


Yes, that's just the API and no GUI components. I only had that as a separate download earlier but it was a very frequent question how to remove the Control Panel applet and how to include just the API components without the Control Panel applet in various projects, as well as compatibility issues with extremely GUI stripped down Windows builds. So I decided to include it in the standard package (although not automatically installed).
 

It seems you deleted a more recent version of the readme.txt that we found in the last build of the version 2.0.9. There were mentions of Windows 10...


Oh, I'll check that!
 

No compilation for imdisk.sys x64? But I see several small changes in the source...
We can use install.cmd to check the system version and then use a dedicated .inf file to install the version 2.0.9 only for Vista x64 (and by using the .inf file to check the architecture, which is difficult to do in a reliable way in a batch file).

 
There are no practical changes actually. There is a different return value nowadays when someone tries to open a device that is about to be removed. That was some kind of experiment to see if that could help in some scenarios against devices hung in a removing state. But as far as I know it did not change anything in practice. Other changes are more a kind of tidy-up-code changes and nothing that actually changed any practical code behavior. So, like I said in a comment in one of the other threads, as I see it there is no point rebuilding x64 versions at this point considering the problem with new certificates on Vista x64/Server 2008 x64.



#3 Olof Lagerkvist

Olof Lagerkvist

    Gold Member

  • Developer
  • 1416 posts
  • Location:Borås, Sweden
  •  
    Sweden

Posted 19 November 2018 - 09:23 PM

There were also changes to awealloc between 2.0.9 to 2.0.10 that will be ignored for x64 architecture because of this. There is a new feature that when allocated memory has been extended and more memory allocated, it can release that memory again if the size of the memory block is later reduced again. This is not of much interest for ImDisk users though, at least I cannot think of a scenario where it would be possible to use it with ImDisk. It was added for another project that used awealloc as storage backend for an in-memory data that could shrink and where it was useful if awealloc could unallocate that memory again.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users