Jump to content











Photo
- - - - -

Discalot

windows disc pe iso build iso deployment disc compiler oscdimg gui oscdimg

  • Please log in to reply
17 replies to this topic

#1 Tokener

Tokener

    Frequent Member

  • Developer
  • 378 posts

Posted 02 July 2017 - 04:30 PM

*
POPULAR

Posted Image

File Name: Discalot
File Submitter: Tokener
File Submitted: 02 Jul 2017
File Updated: 26 May 2023
File Category: Tools

Discalot - the disc compiler

Frontend to MS-oscdimg.exe

If you want to compile an image, bootable or not, you propably have assembled your disc-files in a folder.
Discalot is assisting you to create an image of this directory structure.
Choose a custom boot sector or two (UEFI), to extend boot options.
Various options for file system (UDF, Joliet, ISO 9660) are provided.
Use the whole spectrum of oscdimg command line options in a graphical user interface.

Explorer context menu can be extended by
Discalot(_x64).exe /s [Options]

Run
Discalot(_x64).exe /?
for details.

Select your custom oscdimg.exe to use, in the GUI.
Discalot is tested with oscdimg [build 2.56] on Windows7x64 and Windows10x64.

MS-oscdimg.exe (Microsoft CD/DVD Premastering Utility) is part of Windows® Automated Installation Kit (AIK).

By GetWaikTools
(http://www.msfn.org/...s/?_fromLogin=1)
you can download all (or single) waik tools without downloading any full ISO.

Password for older archives (up to 220630): discalot

Latest version is not encrypted as it contains an ISO file which should not be objected by virus scanners. You can extract this file or mount it as virtual disc.

Enjoy compiling your discs
T.

Click here to download this file
  • Brito, ambralivio and alacran like this

#2 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 06 July 2017 - 07:35 AM

Hello my good friend.

 

Hope you are fine.

 

I am glad you make your tool public, I assume this is a new build and renamed Discom, Is that right?

 

If my assumtion is right, let me suggest you to let the other members of the forum and occasional visitors know this tool may also use grldr (from grb4dos) as boot sector in order to make a Multiboot DVD with several ISO's on it called from menu.lst

 

Non writable media is always the safest way to deal with potentially infected PC's

 

Also not all people who visit this forum is an advanced user, so I think it would be good to explain a little more how to use it, just as you explained me on PM (very clearly by the way).

 

A little promotion is always good, particularly for a good and usefull tool like this.

 

Your friend

 

alacran


  • Tokener likes this

#3 Tokener

Tokener

    Frequent Member

  • Developer
  • 378 posts

Posted 07 July 2017 - 07:18 AM

Dear alacran,
good to hear these words from you.
 

I assume this is a new build and renamed Discom, Is that right?


Indeed, I had to rename it to Discalot because the other name is owned by a company.
Checked it too late.
 

If my assumtion is right, let me suggest you to let the other members of the forum and occasional visitors know this tool may also use grldr (from grb4dos) as boot sector in order to make a Multiboot DVD with several ISO's on it called from menu.lst


Yes, you are right, you can use Discalot/oscdimg to create grub-discs by selecting grldr as bootloader.
 

Also not all people who visit this forum is an advanced user, so I think it would be good to explain a little more how to use it, just as you explained me on PM (very clearly by the way).


Thank you for this good advice.
I will try to extend the help-file for Discalot.
 

A little promotion is always good, particularly for a good and usefull tool like this.


I really appreciate this, and hope the tool will make it easy to create usefull discs.

Sincerely T.

Btw. New Version: download

A little walkthrough: "How to create a boot-disc"

-Install Discalot by the /s switch or [File]-[Extend Context Menu].
-Set oscdimg.exe by -> Program -[Select].
You can skip this if you have a copy of "oscdimg.exe" in the Discalot-folder.

Preparation: Mount a Windows7-Disc-ISO to drive or put a Windows7-Disc to your DVD-device. (also Win8 or Win10-discs will do)

Now you are ready to create your ISO.

-Select context menu "Make my Disc" by right-click on this drive.
-When "Select bootloader" dialogue-window appeares - select etfsboot.com from inside the \boot folder.
The provided etfsboot.com is the default bootloader for Win7-8-10 discs.
-Then you are asked where to store the ISO-file you want to create.
By default names are suggested for label and file-name.
Finally the User-Interface shows all parameters to build the ISO.
-In the [Compile]-Tab press [Create Image] to start the building process.

The procedure is similar if you choose a folder as source.

--------------------------------------------------------------
Parameters by bootloader:
By selecting "etfsboot.com" the script knows what parameters are to be set for NT6 discs.
Selecting "bootsect.bin" lets the script know that you want to build a NT5 disc.
Also the script knows what settings "grldr"-discs require if you choose it as bootloader.


  • alacran likes this

#4 Tokener

Tokener

    Frequent Member

  • Developer
  • 378 posts

Posted 19 June 2019 - 10:12 AM

 

 

 

Dear friends of the ISO file format

there is a new build for Discalot.

New Version 190617: download

 

changelog:

    -Users without administrative rights can extend the shell within their profile.
    -default shell extensions for directory and drive are moved to "HKEY_CURRENT_USER\Software\Classes\..." to provide different settings for users.
    -Admins can extend the shell for all users by /au switch at command line.
    -on PE-systems "HKEY_LOCAL_MACHINE\Software\Classes\..." is used.
    -different oscdimg files can be used for different OS-Architectures by locating files in %OSARCH%-folder (X86 / X64).
    -changed default behavior to "trackless-mode", Config- and Log-File are only saved "on demand".
    -added "Elevated Rights Detector"
 

 

enjoy   T.

 

 

 


  • alacran likes this

#5 midas7

midas7
  • Members
  • 1 posts
  •  
    Greece

Posted 04 June 2020 - 09:21 PM

Dear ReTokener,

 

Thank you very much for the very useful utility.

I think it is the only GUI utility that can be used to create a bootable DVD/ISO (simultaneous BIOS and UEFi).

 

Could you please let me know how to use isolinux.img as BIOS bootloader?

 

IMGBURN has an option "patch boot information table" when choosing isolinux.img as bootloader to boot the created ISO properly.

 

Is there a similar option in your utility?

Can I use isolinux.img as BIOS bootloader instead grub (grldr)?

 

Thank you in advance.

 

Midas7



#6 Tokener

Tokener

    Frequent Member

  • Developer
  • 378 posts

Posted 05 June 2020 - 12:15 PM

Hi Midas7

thanks for your friendly evaluation of Discalot.

 

Could you please let me know how to use isolinux.img as BIOS bootloader?

'cause I never created a Linux boot disc I don't have an answer to your question.

 

But here are friendly people on the board who might have an answer for you if you ask by opening a new thread.

 

Regards   T.

 
 

 

 



#7 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 16066 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 05 June 2020 - 03:41 PM

Dear ReTokener,

 

Thank you very much for the very useful utility.

I think it is the only GUI utility that can be used to create a bootable DVD/ISO (simultaneous BIOS and UEFi).

 

Could you please let me know how to use isolinux.img as BIOS bootloader?

 

IMGBURN has an option "patch boot information table" when choosing isolinux.img as bootloader to boot the created ISO properly.

 

Is there a similar option in your utility?

Can I use isolinux.img as BIOS bootloader instead grub (grldr)?

 

Thank you in advance.

 

Midas7

The issue is somewhat talked about here:

https://msfn.org/boa...-torito-images/

 

Are you sure it is isolinux.img (and not isolinux.bin)?

 

Basically, that provision by IMGBURN is correct (and actually needed) if you use Isolinux versions earlier than 2.12, from 2.12 onwards it is not needed anymore as the boot-info-table is already correct in the isolinux. :)

 

We are talking of BIOS here, no idea about UEFI booting of Isolinux, there is a thread on Syslinux mailing list, including a "workaround" by ady for using oscdimg for images larger than 32 MB, but possibly in the meantime things have changed :unsure::

https://www.syslinux...ril/025091.html

 

:duff:

Wonko



#8 Tokener

Tokener

    Frequent Member

  • Developer
  • 378 posts

Posted 30 June 2022 - 06:06 AM

Dear friends

First of all I apologize for the bugs that were in the script, undetected by me.

There is a new version 220630 and the bugs are (hopefully) fixed.

The script should now work properly.

 

 

    -added: optional command line for oscdimg commands.
    -bug fixed: delay of report (if activated).
    -bug fixed: not resolving symbolic links.
    -bug fixed: exclusion filter not working.
    -bug fixed: bootOrder.txt not recognized.

Greetings
T.

 

 
 

 

 



#9 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 02 July 2022 - 02:03 AM

Hi my good friend.

 

If using WIMISO profile with following entries when loading the ISO using grub4dos for MBR it boots fine, but if loading the ISO from grub4dos for UEFI, it doesn't boot.

 

alacran

Attached Thumbnails

  • WIMISO.png

  • Tokener likes this

#10 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 02 July 2022 - 02:27 PM

If the ISO file is builded by Win10XPE, when loaded by grub4dos (MBR or UEFI versions) it boots fine.

 

Following are the commands used during building the ISO file by means of mkisofs.exe in Win10XPE:

 

 

    &Echo.&mkisofs.exe -iso-level 4 -udf -r -force-uppercase -duplicates-once -volid #$q%ProjectName%_%Architecture%#$q -hide boot.catalog -hide-udf boot.catalog -b #$qboot/etfsboot.com#$q -no-emul-boot -boot-load-size 8 -eltorito-platform efi -no-emul-boot -b #$qefi/microsoft/boot/efisys.bin#$q -o #$q%ISOFileName%#$q #$q%GISO%#$q",%GTools%

 

alacran



#11 Tokener

Tokener

    Frequent Member

  • Developer
  • 378 posts

Posted 02 July 2022 - 09:34 PM

Hola my friend  :hi:

looking at the picture in post #9, there is no UEFI bootrecord specified.

 

These settings make my ISO boot successfully in BIOS and UEFI environment.

 

Zwischenablage01.jpg

 

Zwischenablage02.jpg

 

hope this helps   T.


  • alacran likes this

#12 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 03 July 2022 - 03:50 AM

Thanks, all is working now as expected.

 

And I have a suggestion for you:

 

From the user point of view, the profile names are not very intuitive:

 

Profile WIMISO  >>>  Means only MBR bootable  >>>  Maybe renamed to MBR_ONLY could be a good option.

Profile UEFI  >>>  Means MBR and UEFI bootable  >>>  Maybe renamed to MBR+UEFI could be a good option.

 

alacran


  • Tokener likes this

#13 Tokener

Tokener

    Frequent Member

  • Developer
  • 378 posts

Posted 03 July 2022 - 04:49 AM

Dear friend

Glad to hear script is working as expected.

Thank you for your suggestion.
Your objections to the naming are valid, however, at the moment I can't say why i chose the profile names this way.
The user has, on the other hand, the option to create a more expressive profile(name).

Sorry if there is any inconveniance.

 

Best regards   T.



#14 Tokener

Tokener

    Frequent Member

  • Developer
  • 378 posts

Posted 03 July 2022 - 04:57 AM

Note:

there is a recent version 220703 that better eliminates possible misclicks.

 

Regards   T.



#15 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 03 July 2022 - 05:46 AM

Once the user understands the meaning of the Profile names you used, there should not be any problem selecting the right profile for the current task they want to run.

 

Thanks for your new version. Just downloaded it.

 

alacran


  • Tokener likes this

#16 Tokener

Tokener

    Frequent Member

  • Developer
  • 378 posts

Posted 03 July 2022 - 06:00 AM

Once the user understands the meaning of the Profile names you used, there should not be any problem selecting the right profile for the current task they want to run.

Hola my friend

True, so as soon as I find more suitable expressions it will be changed considering your suggestions.

 

Best regards   T.



#17 Tokener

Tokener

    Frequent Member

  • Developer
  • 378 posts

Posted 03 July 2022 - 07:41 AM

Hello, it's me again ...

 

I found, the profile WIMISO is valid and loaded as soon as etfsboot.com is selected as bootloader. (from shellmenu: 'Make my Disc')

Profile UEFI is therefore an extended version of the WIMISO profile, as it is adding a second / alternative bootloader for UEFI environment. Apart from this, the two profiles are identical.

 

For the sake of completition it should be mentioned that grub-discs are created with the BOOTSECT profile.
The BOOTSECT profile is recognized and loaded if 'grldr_cd.bin' or 'grldr' is selected as bootloader.

The name-giving bootloader 'bootsect.bin' is used for Win_XP discs.
BCDW discs also use the BOOTSECT profile, when 'bcdwboot.bin' is selected as bootloader.

 

Hope this brings some clarification.  

 

Best regards   T.



#18 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 03 July 2022 - 09:17 PM

So the logic in your program is based in the selected boot loader, that automatically selects an appropriate profile for that case.   That sounds good to me for non advanced users, that don't have an idea of what profile to use.

 

To summarize, and have all info together in one post, valid bootloaders for each profile are:

 

WIMISO Profile  >>>  MS bootloader only MBR bootable, where bootloader is \boot\etfsboot.com

UEFI Profile  >>>  MS bootloader MBR and UEFI bootable, where bootloaders are \boot\etfsboot.com + \efi\microsoft\boot\efisys.bin (or efisys_noprompt.bin)

 

BOOTSECT Profile  >>>  Is used in following cases:

  • grub4dos (MBR) bootable-discs where the loader is grldr_cd.bin or grldr
  • Win_XP discs where the bootloader is bootsect.bin
  • BCDW discs also use the BOOTSECT profile, where bootloader is bcdwboot.bin

 

 

Additionally In case of advanced users having more knowledge of the profiles, and its respective use (as mentioned in previous paragraphs), they can use following procedure:

  1. Select the folder containing the info they want to include into the ISO.
  2. Select the name and path for future ISO.
  3. Select the profile they want to use in Compile Tab.
  4. Open Boot Tab and select the loader or loaders as required.
  5. Open again Compile Tab and compile the ISO.

I hope this info can be useful to help users to prevent selecting the wrong loader, or forget to add the second loader if it is required in that profile.

 

So if using previous procedure, selecting the right profile, followed by selecting the respective loader(s) are the key parts.

alacran


  • Tokener likes this





Also tagged with one or more of these keywords: windows disc, pe iso, build iso, deployment, disc compiler, oscdimg gui, oscdimg

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users