Sorry for this newbie question.

I have a simple question:

Assume I have a completely portable small program in folder

D:\foo\bar\base\aaa.exe

As far as I understand when I want to add this program to the target installation I have to write/modify a script

for WinBuilder. But how do I do this in detail?

1.) How do I add the whole folder D:\foo\bar\base\ to the target's \Programs\ folder?

2.) How do I create a link to aaa.exe in Start menu?

3.) How do I let aaa.exe auto-start at boot time?

Thank you

Peter

Hi guys!

I'm trying to come up with a way to wipe the MBR/GPT of all the drives within a system booting only to UEFI Secure Boot, without CSM. I know I can change in UEFI the settings and enable CSM but I need it to work this way.

I have a USB drive, formatted with FAT32, bootmgr, copied boot and efi folders. Tested it and boots fine in BIOS and UEFI. But now I'm looking for a way to also do a wipe of mbr/gpt of every existing disk in the system.

Here's the way i'm thinking:

UEFI -> bootmgr -> wipe command

or something like this

UEFI -> bootmgr -> very small winpe.wim -> wipe command

Is there any possibility of running a command via bootmgr, without loading a .wim image, that can kill the partition table?

I would not prefer loading a full wim due the delay of loading the image. Something very similar to what Wonko posted over this thread http://reboot.pro/topic/20677-fast-bootable-alternative-to-dban/#entry194793but something that will work with bootmgr.

Thank you

hI guys what is wrong ?

ERROR REPORT ( 12/30/2016 08:40:52 )
Please submit this error report to developer.
Operating System version  :Microsoft Windows NT 6.2.9200.0
.NET Framework version    :4.0.30319.42000
Error Message            :
Could not load file or assembly 'PGK.Extensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f93e897f802ddcb7' or one of its dependencies. Das System kann die angegebene Datei nicht finden.
StackTrace               :
   at A.V.D()
   at A.V.D(ImageItemBase , ProcessLog )
   at A.KB.D()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

In Windows 7, Native VHD boot is currently supported only on Ultimate and Enterprise versions and is disabled by a license policy on other versions of Windows. This article/tutorial shows how Native VHD boot can be enabled on unsupported versions of Windows 7 as well.

The post Native VHD Boot on unsupported versions of Windows 7 appeared first on AgniPulse.

DEFAULT MENU.C32

PROMPT 0



LABEL pe21

MENU LABEL ^P)  Boot Custom Windows PE 2.1

KERNEL PE21BOOT.BIN



LABEL pe21.iso

MENU LABEL ^Q)  Boot Custom Windows PE 2.1 ISO with memdisk

KERNEL MEMDISK

APPEND iso initrd=PE21.ISO

ISOLINUX 3.07 03/01/2005
Copyright © 1994-2005 H. Peter Anvin
.
Initial menu has no LABEL entries!
boot:

Set ActionCmd1_1   = "isolinux PE21BOOT.BIN"

Set ActionCmd1_2   = "isolinux MEMDISK iso initrd=PE21.ISO"

I happened to find this very nice resource (which I had never seen cited before):
http://goncharov.pp.ru/en/osboot.htm

 

This tool set is designed for fast, easy and reliable booting of your operating system or one of the existing OS to PC memory from floppy disks, flash-drives, hard drives from partitions MBR, EBR and GPT including that beyond 2TB limit and with file systems FAT12/16/32, exFAT, NTFS, Minix1/2/3, Ext2/3/4, from CD/DVD-disks with file system ISO-9660 and from ISO-images written to the USB flash-drives (USB-ISO) without installing complicated multistage loaders.

whether it does deliver as it promises (without collateral effects) is to be seen/checked, but the approach is really very, very interesting.

The Author posted it on Osdev, here:
http://forum.osdev.org/viewtopic.php?f=2&t=25116&sid=a1cca77a7b03f45f64b44ee5911c6f07

Unfortunately a good half (if not 3/4) of the fun is taken away by the license that - for most of the stuff - is Freeware (which is good) but without source provided and with separation of components not allowed .

(while having the asm source files for the MBR's and bootsectors would provide no end of learning).

This (or that ) bootsector or piece of MBR code could be very useful for this (or that) project but the need to redistribute the whole package (even if tiny, a .zip file with more than 30 files) and the prohibition to modify them represents IMHO a roadblock.

There is seemingly support for (besides Linux and its own mini-kernel) GRUB2, Syslinux and grub4dos (though for now obsolete versions of them) and for windows loaders (again here it will have to be seen how anything post-2013 is compatible).

The mksys.exe tool modifies (patches) these second stage loaders replacing the initial loader with its own, so the thingy is essentially "version specific".

The mini-kernel, kernel.sys is however fully open source and in itself is very good for people wishing to learn  assembler.

Wonko

Hello everyone!

I'm new and was trying to use bootx to put multiple ISO's onto one usb drive. I feel I found some really great tools to put on a USB drive using the bootx program. I'm super stoked and excited to get this done, except I ran into a few issues.  Can you guys help me out by telling what this error log means and how I can correct the issue? I selected grub4dos and also tried the recommended syslinux. When choosing to boot this PE I choose the first option on the list, USB iso Image emulation.

I was trying to put a couple antivirus iso's and also something called Gandalfs windows PE. Its a boot disc (for usb) that lets you modify your windows to help fix it (registry, antivirus etc). The original website is called windowsmatters.com

I want to put a few of these on the same USB because there is different versions depending on which windows you're using. 

Below is the error log, thank you all again for you help. It is much appreciated.

ERROR REPORT ( 12/21/2016 21:32:03 )
Please submit this error report to developer.
Operating System version  :Microsoft Windows NT 6.2.9200.0
.NET Framework version    :4.0.30319.42000
Error Message            :
Could not load file or assembly 'PGK.Extensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f93e897f802ddcb7' or one of its dependencies. The system cannot find the file specified.
StackTrace               :
   at A.V.D()
   at A.V.D(ImageItemBase , ProcessLog )
   at A.KB.D()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()




ERROR REPORT ( 12/21/2016 21:41:32 )
Please submit this error report to developer.
Operating System version  :Microsoft Windows NT 6.2.9200.0
.NET Framework version    :4.0.30319.42000
Error Message            :
Could not load file or assembly 'PGK.Extensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f93e897f802ddcb7' or one of its dependencies. The system cannot find the file specified.
StackTrace               :
   at A.V.D()
   at A.V.D(ImageItemBase , ProcessLog )
   at A.KB.D()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()




ERROR REPORT ( 12/21/2016 21:43:55 )
Please submit this error report to developer.
Operating System version  :Microsoft Windows NT 6.2.9200.0
.NET Framework version    :4.0.30319.42000
Error Message            :
Could not load file or assembly 'PGK.Extensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f93e897f802ddcb7' or one of its dependencies. The system cannot find the file specified.
StackTrace               :
   at A.V.D()
   at A.V.D(ImageItemBase , ProcessLog )
   at A.KB.D()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()




ERROR REPORT ( 12/21/2016 21:47:08 )
Please submit this error report to developer.
Operating System version  :Microsoft Windows NT 6.2.9200.0
.NET Framework version    :4.0.30319.42000
Error Message            :
Could not load file or assembly 'PGK.Extensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f93e897f802ddcb7' or one of its dependencies. The system cannot find the file specified.
StackTrace               :
   at A.V.D()
   at A.V.D(ImageItemBase , ProcessLog )
   at A.KB.D()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()




ERROR REPORT ( 12/21/2016 21:48:07 )
Please submit this error report to developer.
Operating System version  :Microsoft Windows NT 6.2.9200.0
.NET Framework version    :4.0.30319.42000
Error Message            :
Could not load file or assembly 'PGK.Extensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f93e897f802ddcb7' or one of its dependencies. The system cannot find the file specified.
StackTrace               :
   at A.V.D()
   at A.V.D(ImageItemBase , ProcessLog )
   at A.KB.D()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()




ERROR REPORT ( 12/21/2016 21:48:58 )
Please submit this error report to developer.
Operating System version  :Microsoft Windows NT 6.2.9200.0
.NET Framework version    :4.0.30319.42000
Error Message            :
Could not load file or assembly 'PGK.Extensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f93e897f802ddcb7' or one of its dependencies. The system cannot find the file specified.
StackTrace               :
   at A.V.D()
   at A.V.D(ImageItemBase , ProcessLog )
   at A.KB.D()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()




ERROR REPORT ( 12/21/2016 22:01:58 )
Please submit this error report to developer.
Operating System version  :Microsoft Windows NT 6.2.9200.0
.NET Framework version    :4.0.30319.42000
Error Message            :
Could not load file or assembly 'PGK.Extensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f93e897f802ddcb7' or one of its dependencies. The system cannot find the file specified.
StackTrace               :
   at A.V.D()
   at A.V.D(ImageItemBase , ProcessLog )
   at A.KB.D()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()




ERROR REPORT ( 12/31/2016 16:19:49 )
Please submit this error report to developer.
Operating System version  :Microsoft Windows NT 6.2.9200.0
.NET Framework version    :4.0.30319.42000
Error Message            :
Could not load file or assembly 'PGK.Extensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f93e897f802ddcb7' or one of its dependencies. The system cannot find the file specified.
StackTrace               :
   at A.V.D()
   at A.V.D(ImageItemBase , ProcessLog )
   at A.KB.D()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

Hi,

the latest UrBackup Server version uses ImDisk to mount VHD and compressed VHD files it previously backed up.

This works very well, so from me and the (future) users a big thank you!

Some potential issues and perhaps things that can be improved (but must not as it already works as is):

• The UrBackup Server installers now bundle ImDisk. Please tell me if I should change something there, or if I should stop bundling it, specifically because it conflicts if the User installs/uninstalls ImDisk separately
• Specifically bundling would be easier if it had a "proper" installer (like NSIS or MSI). If you need some help I would be glad to
• It stops ImdiskSvc in order to service the user space named pipe itself. It would be better if there were more than one named pipe so ImdiskSvc can continue to run
• I am passing the VHD(z) name as hostname, which works, but isn't as you intented probably . The ImDisk server code is here btw: https://github.com/uroni/urbackup_backend/blob/dev/fsimageplugin/ImdiskSrv.cpp

If you need help getting a new driver version attestation signed, I'd be able to do that.

Thanks!

Hello guys,
I have a DVD with WIN7PE SE that works perfectly,

but on the new notebook you do not see me USB ports being in version 3.0

there is the possibility to insert native support to USB 3 to my win7pe without having to resort to specific driver for each notebook?

thanks

Hello guys,
I have a CD with LiveXP that works perfectly,

but on the new PC does not boot
I get the blue screen saying that my ACPI is not supported

can I edit my LiveXP to fix this problem?

thanks

Hi all

http://www79.zippyshare.com/v/JqtYBj2O/file.html

this is link for new driver masstorage for windows XP

Who can fix the error that occurs during the integration with DPBASE?

this is the error:
dpbase reporting the error:
AutoIT Error
"Line 13227 (File c: \ test \ DPs_BASE.exe);
Error: Subscript Used with non-Array variable.

Hello reboot!

Thanks for you help last time. I have a new problem. So I was able to reboot Gandalfs PE. However it had limited capability and no internet, which I have never seen before. When I boot with rufus, it works perfectly, but I want to use xboot, so I can put multiple tools on one USB. I bought a 32 GB flash drive for this purpose.

This is what the error log showed from the limited capability PE. I was wondering what advice you can give me or what adjustments I can make to get this fully functional. I felt this was the appropriate place to post this since I think its a problem with xboot, or the settings I am choosing.

CdUSB.Y or ISO NOT found !
Win10PESE can not mount and access files of your CD/DVD, USB, ISO on drive Y:

Possible Reason and Solutions :
1) You are using UFD (USB Flash Disk) as boot media formatted in NTFS.
---> Use FAT32 with UFD :>    ( Format UFD with FAT32).

2) You are not using .iso boot (You are using RealCD/DVD, BCD BOOTMGR, grub4dos BOOTMGR, etc.).
---> Check that the flag file CdUsb.Y is at the root of your media.
---> Your drive remained to the state "Not Ready" (More than 30 seconds) for a hardware reason.
---> Your drive is not recognised (driver missing or whatever, check if you can see your CD or Usb drive letter on explorer).

3) You are using .iso boot (grub4dos, isolinux, etc.) but you changed the build .iso name or path of your iso (ex: Win10PE_x86.iso, \Images\Win10PE_x64.ISO).

* If you use all from ram (all inside .wim) ignore this warning ;).
+ If you need files in your .iso to access, read following.

A) This feature requires imdisk, else will not work.
---> Be sure you have imdisk on your Win10PESE (Enable at Win10PESE\Tweaks).

B) Change your .iso name to the build .iso name (ex: Win10PE_x86.iso ) and put it to the correct path of your bootdrive.
---> Look for the default build configuration in the internal ini file (X:\Windows\System32\MountPEmedia.ini section IsoInfo/IsoName).
---> Rebuild by giving your personal Iso file name\Subfolder in the plugin Finals\Create ISO.

C) Use Win10PESE.ini to specify your personal .iso file name and location (solution for without rebuilding your project with your custom .isoname/subfolder settings).

3b) You are using .iso boot (grub4dos, isolinux, etc.) but .iso file to mount not accessible.
(= you can not see your Win10PESE iso file with explorer).
---> Driver missing -> add driver for your disk.
---> Some windows settings or software which disables mounting drives at boot -> disable such setting/software.
---------------------------------------------------------------------------------------------------------------
9) Contact http://spam
----------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------

MountPEmedia.exe : Mount files of your CD/DVD, USB, ISO on drive Y:

Ini File (MountPEmedia.ini) :
  [Settings]
  ProjectName=Win10PESE
  MountDrive=Y:
  SearchFlagFile=Yes
  FlagFileName=CdUSB.Y
  SearchExternalIniFile=Yes
  ExternalIniFileName=Win10PESE.ini
  DesktopWarningLabel=Win10PESE Warning

  [IsoInfo]
  IsoName=Win10PE_x86.ISO

Program Imdisk found in : X:\windows\system32

=====>   Passage : 1
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 2
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 3
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 4
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 5
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 6
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 7
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 8
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 9
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 10
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 11
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 12
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 13
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 14
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 15
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 16
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 17
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 18
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 19
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 20
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 21
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 22
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 23
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 24
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 25
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 26
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 27
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 28
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 29
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 30
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

All drives are ready but without finding CdUSB.Y or the ISO file in the allotted time of 30 seconds ! Exit.

Hey people

I have already used my pendrives as bootable windows installation drives and know how to do it.

But now I want to make a bootable windows (8.1) installation "disk" from my flashdrive, and this flashdrive should be write-protected. (it shouldn't be possible to overwrite the partition)

Here is the chipgenius report : 

 

Description: [E:]USB-Massenspeichergerät(SMI USB DISK)

Device Type:        Mass Storage Device

 

Protocal Version: USB 2.00

Current Speed: High Speed

Max Current: 500mA

 

USB Device ID: VID = 090C PID = 1000

Serial Number: AA00000000004572

 

Device Vendor: PSPlover

Device Name: PSPlover

Device Revision: 1100

 

Manufacturer: SMI

Product Model: USB DISK

Product Revision: 1100

 

Controller Vendor: SMI

Controller Part-Number: SM3257ENAA - ISP 130430-AA-

Flash ID code:      ECD798CE - Samsung K9ABGD8U0B - 1CE/Single Channel [TLC-8K] -> Total Capacity = 4GB

It's an older intenso rainbow stick with an SM3257ENAA chip, and I can't remember to see an option in the manufacture tool.

I hope someone can give me an useful advise   

Hello,

I'm looking into ways of creating a fingerprint of an executable file (for e.g. Windows, but could also be Linux/Mac) based on its internal functions.

What do you think it would be a good strategy to make this possible?

Have some ideas:

1) extract function names (not sure if available)

2) get the code for the function, generate similarity hash of the content

3) other methods?

Right now option 2) seems to be on the spot for this task (assuming a plain executable without UPX or anything of the sort). After extracting the assembler code, it should be relatively straightforward to compare different functions to see if they are similar as done already for other binary comparisons.

Would you know any library (non-copyleft license) and hopefully running on Java that could extract the assembler snippet for each function or a better approach to this goal?

My thanks and happy 2017 ahead!

Hi,

Following a discussion started here, I am releasing this Product Policy viewer.

It can read both an online and offline registry.

It will parse the following key : SYSTEM\CurrentControlSet\Control\ProductOptions\ProductPolicy.

What is good for?

Check enabled/disabled features on your windows (depending on which version you  have).

I am asking the modos over here if adding a write feature to this tool would be considered as encouraging illegal activities.

Note that I did not check yet is writing to an offline registry is actually an option.

Regards,

Erwan