34 replies to this topic

[alacran]

This time I am on 7x64 OS and just replace create.ISO.script on ADK project and only ran this single script using WinBuilder 082, oscdimg selected, ISO was created successfully size is 487 MB.

 

EDIT: New ISO build this time mkisofs selected, ISO was created successfully size is 488 MB.

 

EDIT-2: Made new ISO's builds but this time selected oscdimg & optimize, and also mkisofs & optimize the last one takes longer, but ISO sizes are the same of those previously created without selecting optimize.

[misty]

NOTE - following post by erwan.l moved to here

It is slightly off topic but I could not post it in PEBakery topic (it is locked).

PEBakery normally requires .Net 4.7.1.
This is rather a recent version and you cant always install the latest framework (for whatever reasons - in my case, I am using my work laptop right now).

Creating a pebakery.exe.config with the below text will allow you to use what ever 4.x version you have on your system.
This a rather known/documented trick in the .Net world.
Several "supportedruntime" items can be added.
The software will also use the latest version.

I havent tried with earlier .Net versions.
All depends if PEBakary uses classes/methods found only in latest frameworks.
Note that it could also lead to crashes/inconsistent reasons for the above reason.

Provided that the developper is OK, this would ensure greater compatibility with various systems outthere.
This is one of the main issues when distributing .Net apps : missing/wrong .Net framework...

Still, I thought I would share...

More details here.

<configuration>
   <startup>
      <supportedRuntime version="v4.0"/>
   </startup>
</configuration>

Hope you don't mind Erwan - it seems more appropriate to have in the new PEBakery subforum.



Misty

P.s. It's also useful to test/exercise my mod powers every now and again

[misty]

...EDIT-2: Made new ISO's builds but this time selected oscdimg & optimize, and also mkisofs & optimize the last one takes longer, but ISO sizes are the same of those previously created without selecting optimize.

The optimize command works well if there are duplicate files (e.g. a Flat Boot WinPE), however I doubt that it will make much if any difference in this build.



Misty

[erwan.l]

NOTE - following post by erwan.l moved to here


Hope you don't mind Erwan - it seems more appropriate to have in the new PEBakery subforum.



Misty

P.s. It's also useful to test/exercise my mod powers every now and again

 

Thanks a lot.

I should have known better and do it in the first place actually.

Apologies for the spam

 

Cheers,

Erwan

[alacran]

The optimize command works well if there are duplicate files (e.g. a Flat Boot WinPE), however I doubt that it will make much if any difference in this build.



Misty

 

Yes, I was thinking same thing: If there is nothing to optimize size will be the same, and it was (exactly same number of bytes).

 

But I had to try all ways and report results. It was a chance to also verify Dated Isos having 4 of them with diferent date-time (for minutes only).

 

EDIT: I think folder DOWNLOADS can be deleted after install ADK 10.0.16299 or the version downloaded.  And I assume once it is installed it will not be downloaded again, Is this right?

[alacran]

Using boot.wim from ADK Project on MistyPE Project

 

Used this procedure:

Once got boot.wim from ADK Project. (located on ADK\ADK_workspace\ISO_Root\sources\boot.wim)

Go to MistyPE Project.

Go to tools - Cache Files - Option 1 and follow instructions.

1] Select 1 as this is boot.wim from ADK (single index).

2] Select as required.

3] Select as required.

4] PATH to WinPE source (.wim) you can select the boot.wim to be used. (Click on ? for more info).

5] PATH to Windows source (.wim or .esd) here you select your install.wim/esd. (Click on ? for more info).

Run the single Script (NOT the project) to create the cache.

    

Latter on MistyPE (2018-01-21):

1] Attemp to use Existing Cache? YES

2] Select cache
 

3] SysWOW64 Select as required.

 

4] Image number. Select 1 as this is boot.wim from ADK (single index).

   
Select all programs you want and run the project.

 

 

Build was successful, not a single problem. Iso size 682 MB.

[misty]

Thanks alacran.

I take it that you have not managed to break it yet then (as in find significant build errors)? At least not in normal usage.

Misty

[alacran]

Thanks alacran.

I take it that you have not managed to break it yet then (as in find significant build errors)? At least not in normal usage.

Misty

 

It starts getting boring, I'm doing my best effort to break it, but it resist all my attempts .

 

By the way: I think folder DOWNLOADS can be deleted after download and install selected version of ADK.   And I assume once it is installed it will not be downloaded again, Is this right?

 

alacran

[misty]

It starts getting boring, I'm doing my best effort to break it, but it but resist all my attempts .

Haha. Keep on trying. It's thanks to testing and feedback that the project is fairly robust if used sensibly.
 

...By the way: I think folder DOWNLOADS can be deleted after download and install selected version of ADK.   And I assume once it is installed it will not be downloaded again, Is this right?...

In most cases it can be deleted. As I personally end up reverting to a clean backup once every couple of weeks I prefer to avoid the need to download an ADK every time I want to reinstall it.

I can easily add another button somewhere to delete it - perhaps in the download script itself.

Misty

[alacran]

I can easily add another button somewhere to delete it - perhaps in the download script itself.

Misty

 

I do not see a need for it, this folder is very easy to find and name is in capital letters, so I think anybody can find it.

 

alacran