Jump to content











Photo
* * * * * 2 votes

multiPE

win7pe vistape multiboot pe3 livecd pe2 pe1

  • Please log in to reply
595 replies to this topic

#576 JanuszChmiel

JanuszChmiel

    Frequent Member

  • Advanced user
  • 201 posts
  •  
    Czech_ Republic

Posted 03 October 2014 - 08:01 PM

Dear Peter,

Yours latest stable MULTIPE is really outstanding. Because i have configured it to allocate as little RAM as possible when XP source have been selected, i could use it with NVDA even with The system which have been equipped with only 256 MB of RAM. And i could perform my favourite chkdsk /f /r c: Command. But i have one very, very big plea to You.

Would You try to release new MULTIPE version, which would enable me to use modern harddisks connected to The main board by using SATA controllers?

I Am afraid, that current MULIPE do not contain The necessary mass storage drivers, so eventhough many SATA drivers are being provided, it is not enough to make modern harddisks recognisable by The NT kernel when booting live CD based on XP source.

Or, there is second possibility, script for adding SATA drivers must be chosen by Winbuilder context menu.

 

It would be gread, if support of modern harddisks would be possible at least like a choice from some Winbuilder script.

What do You think about my plea?

 

I can not help myself, but classic explorer.exe from XP is The best tool for blind users to browse files of The corrupted systems. And because UI automation do not have to be used by screen reader to get necessary information about chosen file or folder, browsing by communicating with syslistwiev32 class name without UI automation is really much more faster. I also love detailed list style of Windows Explorer from Windows XP.

I can not modify LX155 which You have made to run faster to use NVDA.

I can never get NVDA to work and combining scripts from MULTIPE with LXP155 which You have redesign to work faster can not be simply used.

 

I can not combine myself The necessary scripts to enable support of modern harddisks.

Thank You very much for Yours help and answers.

With kindness regards.

 

Janusz Chmiel



#577 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12701 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 23 November 2015 - 05:55 PM

Version 78 is online.

 

Some smaller bugs are fixed which could become active in the first builds.

 

The project is closed now.

 

Following the fact that WinBuilder 8x is no longer supported, also multiPE support ended.

 

Peter



#578 Chris_H

Chris_H
  • Members
  • 6 posts
  •  
    England

Posted 21 June 2016 - 01:05 PM

Version 78 is online.

 

Some smaller bugs are fixed which could become active in the first builds.

 

The project is closed now.

That's a shame, because v78 fails to boot for me (BSOD after stuck on the Windows boot screen for some time), while v77 works just fine.  (I've tried every variation I can think of to make it work.)

 

Following the fact that WinBuilder 8x is no longer supported, also multiPE support ended.

Bah, WinBuilder 2015 doesn't even boot for me on 50% of machines I try it on (says it can't find the boot drive or something), where-as old WinBuilder projects were usually very reliable.



#579 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 21 June 2016 - 02:34 PM

That's a shame, because v78 fails to boot for me (BSOD after stuck on the Windows boot screen for some time), while v77 works just fine.  (I've tried every variation I can think of to make it work.)

 

 

 

Bah, WinBuilder 2015 doesn't even boot for me on 50% of machines I try it on (says it can't find the boot drive or something), where-as old WinBuilder projects were usually very reliable.

Verbesserung/Schlimmbesserung/Verschlimmbesserung?  :w00t: :ph34r:

 

:duff:

Wonko



#580 Chris_H

Chris_H
  • Members
  • 6 posts
  •  
    England

Posted 21 June 2016 - 06:13 PM

@Wonko

Sorry, I don't speak German.  (And neither does Google Translate, apparently.)



#581 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 22 June 2016 - 08:34 AM

@Wonko

Sorry, I don't speak German.  (And neither does Google Translate, apparently.)

It was only a quick joke for Peter. :)

 

Verbesserung means "bettering", "improvement".

German has also two other words, Schlimmbesserung (little used AFAIK)  and Verschlimmbesserung (more used I believe):
http://krautblog-ulr...mbesserung.html

http://betterthaneng...sserung-german/

https://en.wiktionar...chlimmbesserung

that both mean "disimprovement" or "worsening" :w00t:, but it has somehow the meaning that it is the result of someone attempting (often with good will, and in good faith)  to improve something, but failing at it :ph34r: and thus make it worse than before.

 

:duff:

Wonko



#582 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12701 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 22 June 2016 - 03:35 PM

That's a shame, because v78 fails to boot for me (BSOD after stuck on the Windows boot screen for some time), while v77 works just fine.  (I've tried every variation I can think of to make it work.)

 

 

 

Bah, WinBuilder 2015 doesn't even boot for me on 50% of machines I try it on (says it can't find the boot drive or something), where-as old WinBuilder projects were usually very reliable.

I'm not sure whether you want to get help, or just complain?

 

To 1:

"I've tried every variation" is just a non-constructive complain giving no chance to help. :whistling: Please enum the hundreds of variations you tried.

It is not wise to want to have allways the latest version of an application, independent of you want to fix an issue of the current install.

Never change a running system!

Why using v78 when v77 fullfills your requirements? :dubbio:

 

To 2:

Same common complain w/o useful information:

How many machines do not boot with WB 2015? What's the type of the test machines? MBR or GPT? BIOS or EFI?

Please give an usable table wich can help to find the common property prohibiting a regular boot.

BTW: "Winbuilder 2015" has no logical connection to the current topic.

 

Peter

 

@Wonko: w/o more information I have no opinion whether v78 is a Verschlimmbesserung.



#583 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 22 June 2016 - 03:44 PM

BTW: "Winbuilder 2015" has no logical connection to the current topic.

To be fair it can be rendered in a shorter form, like, you know :

BTW: "Winbuilder 2015" has no logic

:jaclaz:

 

:duff:

Wonko



#584 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12701 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 22 June 2016 - 04:01 PM

To be fair it can be rendered in a shorter form, like, you know :

BTW: "Winbuilder 2015" has no logic

Let's close this discussion with my final statement (in order not to exceed the reboot.pro server's capacity with endless discussions) :lol:

 

Du hast Recht und ich meine Ruhe!

(Google translates to nonsens. It cannot solve the "hast"  related to two items.

The sence: You are right and I relax.

Peter



#585 Chris_H

Chris_H
  • Members
  • 6 posts
  •  
    England

Posted 22 June 2016 - 05:43 PM

@pscEx

 

I'm not sure whether you want to get help, or just complain?

 

Ummm, neither?  I'm mainly reporting the problems I had, in the hope that (1) it might be useful to you or others, (2) I thought you might like to know about problems with it (whether or not development has stopped - maybe you'll want to revert to v77?), and (3) the small hope you might be able to suggest something or possibly even do something.

 

To say I was "complaining" would suggest that I thought I'd been wronged by you somehow, but that would be rather strange when you generously provided that program for free...  (I am a freeware developer myself, so I have some idea how much effort it takes to release something for free.)

 

 

"I've tried every variation" is just a non-constructive complain giving no chance to help. :whistling: Please enum the hundreds of variations you tried.

 

I didn't take any notes, and I didn't think it would be helpful anyhow since I was just making wild guesses.  It would be better if I could somehow identify where it was BSODing, and then work backwards to the cause, but I don't know how to do that unless Windows is booting off a HD (and so has a permanent log file).

 

My comment was merely meant to indicate that I'd made "reasonable effort" to get it to work, and had run out of ideas.

 

 

It is not wise to want to have allways the latest version of an application, independent of you want to fix an issue of the current install.

 

I hadn't used any version until I tried it this week.  v78 was the first version I tried, and it didn't work.  In desperation I tried v77, and that worked straight away to my surprise.

 

The latest version isn't always NECESSARY, but it is NICE to have the latest version, especially since it may fix various bugs.

 

 

Same common complain w/o useful information:

How many machines do not boot with WB 2015? What's the type of the test machines? MBR or GPT? BIOS or EFI?

Please give an usable table wich can help to find the common property prohibiting a regular boot.

BTW: "Winbuilder 2015" has no logical connection to the current topic.

 

The connection seems logical to me, since you said "Following the fact that WinBuilder 8x is no longer supported, also multiPE support ended."  As far as I am aware, WB 8x was discontinued in favour of WB 2015.

 

I never intended to derail the thread with WB 2015 discussion, so I won't elaborate further.

 

P.S.  This editor seems to have the annoying habit of converting "(b)" into an Emotion, and then badly undo it to "( B)" afterwards. :(


Edited by cluecop, 22 June 2016 - 05:52 PM.


#586 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12701 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 22 June 2016 - 06:42 PM

@cluecop

 

Appearently it depends on my bad English, that on your first post got the impression, that you are a "professional complainer".

Your last post changed my opinion.

 

Currently I have only one idea, why v78 boot failes, while v77 is ok: Maybe it is a corrupted (upload >>) download.

 

I'm going to check next week.

 

Sorry for my wrong assumption.

 

Peter



#587 Chris_H

Chris_H
  • Members
  • 6 posts
  •  
    England

Posted 08 August 2016 - 07:05 PM



Currently I have only one idea, why v78 boot failes, while v77 is ok: Maybe it is a corrupted (upload >>) download.

 

I'm going to check next week.

Did you ever check this?  (But I'm doubtful that was the cause.)

 

P.S.  The account verification emails NEVER arrive at GMail addresses (I tried tens of times), but some other email providers are OK.  I guess that there is some problem with your email server, which causes GMail to be 100% certain it's spam.  From a quick check:  Your "reboot.pro" domain name has *no* MX records, so likely GMail considers your email server as unauthorised, and so rejects emails automatically.


Edited by cluecop, 08 August 2016 - 07:15 PM.


#588 Rinxero

Rinxero
  • Members
  • 5 posts
  •  
    France

Posted 26 December 2017 - 04:23 PM

HelloPeter Schlang alias PSCEX and forum members ,

I am Rinxero , a newbie from Paris FRance.

I use a Laptop ASUS F5SL ( 2007) with Windows Visa SP2 and Java JRE6.

 

As my laptop dont offer the Image recovery  capabiliy, I am using Image XML software.

Now in case of my laptop crash , to reload he XML Image, I need to have a windows recovery DVD.

To accomodate my Windows Vista, i have tried to dowload he winbuilder VistaPE on my laptop but it doesnoit work.

I also noticed that multiPE is the first WinBuilder project which builds a PE from XP, Win2003, Vista and Win7 sources.

I am lost because on the First page of MultiPE , it states:

"This track is based on PE3 environnment, and will use a Windows TM  Win7 CD. It builds the PE from source CD Only ".

 

Those 2 statements are antagonist.

Does it need Windows TM  Win7 CD. or Windows Vista that my lapop is running on?

 

I am using the WinBuilder 082.

 

Many thanks for those who can confirm to me a i can run  WinBuilder 082. on my ASUS laptop?

Another question: should i leave the default menu as set or any particular changes?

 

Many thanks

Kind regards,

Rinxero

 

 

 

 

 

 

 

pixel.gif  
 

 



#589 Rinxero

Rinxero
  • Members
  • 5 posts
  •  
    France

Posted 26 December 2017 - 04:26 PM

HelloPeter Schlang alias PSCEX and forum members ,

I am Rinxero , a newbie from Paris FRance.

I use a Laptop ASUS F5SL ( 2007) with Windows Visa SP2 and Java JRE6.

 

As my laptop dont offer the Image recovery  capabiliy, I am using Image XML software.

Now in case of my laptop crash , to reload he XML Image, I need to have a windows recovery DVD.

To accomodate my Windows Vista, i have tried to dowload he winbuilder VistaPE on my laptop but it doesnoit work.

I also noticed that multiPE is the first WinBuilder project which builds a PE from XP, Win2003, Vista and Win7 sources.

I am lost because on the First page of MultiPE , it states:

"This track is based on PE3 environnment, and will use a Windows TM  Win7 CD. It builds the PE from source CD Only ".

 

Those 2 statements are antagonist.

Does it need Windows TM  Win7 CD. or Windows Vista that my lapop is running on?

 

I am using the WinBuilder 082.

 

Many thanks for those who can confirm to me a i can run  WinBuilder 082. on my ASUS laptop?

Another question: should i leave the default menu as set or any particular changes?

 

Many thanks

Kind regards,

Rinxero



#590 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 26 December 2017 - 06:02 PM

@Rimero

The multi-PE was developed to be used on (and for) XP,Vista and 7.

 

It is entirely possible that in some later versions there is a "pre-set" for Windows 7, but that is not relevant, the scripts should work just fine.

 

The issue is, if I understand you correctly, different, most (if not all) Winbuilder projects (including I believe the multi-PE) need as "source" an actual "source", in the form of a "standard" install CD or DVD (or of an .iso image of them).

 

If you do not have an "original" and "standard" Vista installation disc (DVD) or an image of it, you miss the actual "source".

 

In many cases, particularly OEM laptops (such as Asus), never shipped with a "standard" DVD, in some cases you could create an "install" DVD by using a specific OEM program, but often this was not a "standard" install DVD but rather a "recovery" system (such non-standard sources are unsupported, in some cases - but not always - it is possible to recreate a "simil-standard" source, but it involves usually a lot of work).

 

This said, you don't normally need any "particular" PE to run Image XML, I believe you are referring to this one, DriveIMageXML:

https://www.runtime....veimage-xml.htm

 

As a matter of fact they link to Winbuilder based projects that are more up-to-date and that use as source more common (nowadays) OS's, 7, 8 and 10:

https://www.runtime.org/peb.htm

 

But they do offer also a Knoppix based Live CD (you don't need any Windows "source"):

https://www.runtime....ery-live-cd.htm

 

which can restore the images just fine.

 

So, if you miss the "source" and you just want a "recovery media" the Linux Live CD is good enough (and fast enough to "build").

 

As a side note, please remember that DriveImageXML makes images of "drives" (please read as "volumes") and NOT of "disks" (or physicaldrives or "the whole thing") so, while it is always possible to recreate it from scratch, a good idea is to have a backup of the MBR (Master Boot Record or first absolute sector of the disk) besides the DriveImageXML image(s).

 

:duff:

Wonko



#591 Rinxero

Rinxero
  • Members
  • 5 posts
  •  
    France

Posted 28 December 2017 - 10:52 PM

Hello Wonko,

 

THank you so much for your prompt and detailled answer that is enlightening for me.

Just for clarity sake, underneath some extracts from the links you provided, that confirms that in the case of my laptop failure or corruption , i cannot restart with the C drive infected and therefore i need a Windows Preinstallation Environment" different from Windows on C, that will allow me to restaure a DiveimageXML of my whole system including OS windows, Drivers and all personnal medias.

Through its owns backup mode , My Vista SP2 Family edition doesnt offer the facility to backup the above but only my personnal medias. This would be incomplete if C drive with OS is corrupted and if i  need to restaure the complete image of my Laptop

This is the reason why , still from the description provided by WinPE link underneath  , in undersand that PE is the solution to the limitation of my Vista edition.

 

"DriveImage XML is an easy to use and reliable program for imaging and backing up partitions and logical drives.

Image creation uses Microsoft's Volume Shadow Services (VSS), allowing you to create safe "hot images" even from drives currently in use. Images are stored in XML files, allowing you to process them with 3rd party tools. Never again be stuck with a useless backup! Restore images to drives without having to reboot. "

 

"Microsoft's WinPE is a stripped down version of Windows, capable of running from a boot CDs or a USB stick. Its name stands for "Windows Preinstallation Environment". It is used as an installation platform for OEM/Enterprise customers.

WinPE does not require a hard drive to boot, it can run solely from a CD or a USB stick using the memory for dynamic data. This feature makes WinPE appealing for data recovery and system maintenance purposes. In fact, you can run our software from such a boot medium. Since the primary purpose of WinPE is to install Windows, you can expect most hardware to be supported."

 

"

What is WinBuilder?

http://spam/%C2%A0isa free utility from http://theoven.org that helps you to create your own bootable CD or USB stick by extracting the necessary files from your Windows installation DVD. There are currently four WinBuilder versions that work with the respective Windows installation DVD:"

 

"The most compelling benefit of WinPE is that you can run our data recovery software on the affected computer without interfering with the hard drive you want to recover data from. Remember, if you want to recover data you must not write anything to the affected drive, leaving you in trouble if the drive in question was the system (C:) drive. With a bootable CD or USB stick containing our plugin you can recover your data without installing a new operating system."

 

"Here are some typical uses:

  • Do a data recovery with GetDataBack without having to install a complete Windows operating system. Boot from a CD-ROM or USB stick and run the data recovery entirely from there using the RAM for dynamic data. Copy the recovered data to another hard drive or - if you have network access enabled - to a network destination.
  • Edit your hard drive with DiskExplorer. Have unlimited access to any area on any of your drives. For example, after booting from the medium you can let DiskExplorer overwrite your whole drive with zeros.
  • Easily make an image of a drive, locally or through the network.
  • Use a boot medium and restore your system drive from a backup with DriveImage XML.

 

Now some of the kind advises you gave me seems to be contraductory with the above:

1)"This said, you don't normally need any "particular" PE to run Image XML, I believe you are referring to this one, DriveIMageXML:".

As mentioned above "Use a boot medium and restore your system drive from a backup with DriveImage XML"

 

What is the other way than PE to reload Driveimage XML in case of C Sysem drive corruption???

 

2) "As a matter of fact they link to Winbuilder based projects that are more up-to-date and that use as source more common (nowadays) OS's, 7, 8 and 10:".

 

Does it mean that I would not be able to use the PE built with vista to restore Driveimage XML ? If this is the case it contradicts :"Use a boot medium and restore your system drive from a backup with DriveImage XML." ? What would be the interest of Winbuilder for Vista then ?

 

 

Thanks for the advise on new Backup function   Knoppix-Based Runtime Live CD. This is new to me and i need to look into it.

 

3)"As a side note, please remember that DriveImageXML makes images of "drives" (please read as "volumes") and NOT of "disks" (or physicaldrives or "the whole thing") so, while it is always possible to recreate it from scratch, a good idea is to have a backup of the MBR (Master Boot Record or first absolute sector of the disk) besides the DriveImageXML image(s)."

 

a) What is the difference betwwen "Drives" (as volume ) and "Physical Drives"( As disks)? Not clear at all !!! Through my Image backup ( DriveimageXML ) i want to back up the overall drives or Volumes of the Whole LAPTOP. Wouldnt  DriveimageXML just do that and the whole laptop???

 

B) Doesnt drive image XML comprise MBR (Master Boot Record or first absolute sector of the disk)?

 

4) Concerning the source DVD supplied with my OEM asus , 2 DVD have been supplied:

a)  a "Recovery DVD ASUSTeK Computer inc" With the indication " N2496 EN/FR/SP/CS/CT   V1.3 15G356031002 Windows Vista"

B)"F5 Driver & Utility Ver 1.0 F5SL N2631 A5G356219100" " This disc supports Windows Vista 32 Bit Only"

 

 Do you think that they dont comprises the Sandard Windows Install DVD but hat they are the recovery DVD. In which case "it is possible to recreate a "simil-standard" source, but it involves usually a lot of work)" means that i would have to give up this Win Builder solution as i am not IT literate?

 

 

Again , many thanks Wonko for any complementary reactions, explanations and advises you will be able to give.

 

Best regards and Happy New Year!!!



#592 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 29 December 2017 - 03:48 PM

Dont' worry, you are not the first one confused about the whole stuff and with the terminology used (which often is confusing).

 

Simplified (but not much) what you see in the rows of Disk Manager (named as Disk0, Disk 1, etc.) are "disks".

What you see inside the rows are "partitions" (parts of the disks) that contain "volumes". or "drives", i.e. what get a "drive letter" and you normally access in Explorer.

 

A disk is the whole thing and includes:

1) the MBR, or first absolute sector of the device

2) a given number of "hidden sectors", usually 62 or 2047

3) one (or more) partition(s), a partition (if of the type primary) is to all the practical effects the same thing as a "volume" or a "drive", whilst a partition (of the type "extended") may contain one or more such "volumes" or "drives".

4) some unused/excess space (usually at the end, but might be (rarely) in "gaps" between partitions

 

The MBR (Master Boot Record) contains some code and a "partition table" where the addresses of the partitions (that as said are either a "drive" or contain "drives") are located.

 

The DriveImageXML is intended to save/backup the "drive" (which for all practical purposes you can think as the "whatever gets a drive letter in Explorer"), i.e. items in #3 above only.

 

#2 and #4 are normally unused and not useful anyway and there is no reason to save/backup them normally.

 

#1 is instead useful and necessary in a "total" recovery (also sometimes referred to as "bare metal" recovery).

Though it is perfectly possible to re-create the MBR from scratch, using the information contained in the images of the drives, it is not intuitive/easy, particularly in a situation where the user is already stressed by the malfunctioning that led to the need for restoring the backup images. so it is advised to make a copy of it anf keep it together with the saved image(s) of the drive(s), as it costs nothing to do such a copy when creating the backup and having it saves time when/if there is a need for restoring and - for *whatever reasons* - the MBR has been deleted or was corrupted.

 

Think of two different possible disaster scenarios:

1) the disk drive (the device) is working fine and only a volume (or drive) is corrupted and needs to be restored

2) the disk drive (the device) is malfunctioning and you need to replace it and restore to the new device the contents from the backups.

 

In case #1 the image(s) taken with DriveImageXML is/are all is needed.

In case #2 the image(s) taken with DriveImageXML need to be integrated by a newly made or restored MBR.

 

Since it costs nothing (or next to nothing) to make a copy of the MBR, it is a good idea to make one, even if it will be never used.

Some more details in this (via Wayback Machine):

https://web.archive....pic=22984&st=13

 

You can use this little tool, HDhacker:

http://dimio.altervista.org/eng/

don't be misled by the name, it is a plain simple tool useful to save (and restore) a MBR, you want to run it and make a copy of the first sector of the PhysicalDrive (the disk), then save it to a file. You can make sure to select the right PhysicalDrive# (it will very likely be 0, as in a laptop there is usually only a single disk) by checking in Disk Manager, the disk 0 is PhysicalDrive0, the disk 1 is PhysicalDrive1, etc.).

 

Back to the main "Winbuilder", the idea is to create a Windows PE from a "source" install DVD.

The install DVD means a "standard" install DVD from Microsoft or an image of it (.iso), the *need* for an original install DVD is only because the Winbuilder projects are an automated way to create the PE, and it wouldn't be practical/feasible to adapt the project .scripts to each and every slightly different DVD made by OEM's (historically the worst nightmares were the customized install CD's/DVD/s by DELL and HP, as an example).

 

In your case (as it often happens BTW in the last 10 years or so), you don't even have an install DVD, but rather a "recovery DVD", which more or less contains already a WinPE and an image of the disk as it was when it left the factory, the problem is that some of such PE's (cannot say yours specifically) are "narrowed" to automatically apply the existing image (and nothing else)  and thus by running it you would obtain something very similar to the "reset to factory" you may be familiar with regarding smartphones, the device is restored to a point in time before you had it, and thus all your data, preferenmces, settings, etc., etc. are lost.

 

In some case it is very easy to "adapt" the PE inside the "recovery DVD" to a more "generic" PE and/or to adapt it to be the "source" Winbuilder requires, but yes, it implies anyway some IT knowledge, or however the will (and time) needed to learn some fundamentals, so it is not advised in your case.

 

But you can still create a PE downloading a suitable source, such as the VIsta or the Windows 7 AIK as there is no real need that the PE used for restoring is built from exactly the same OS as the one is installed, as a matter of fact it is totally irrelevant what environment is used, as long as it allows the DriveImageXML (and the optional MBR restoring tool) to operate,  in this the good guys @runtime.org made a very wise choice providing an alternative Linux based environment (that - unlike *any* WinPE - merely for copyright/licensing reasons) they can distribute pre-built and ready to be burned/used as recovery environment. 

The Windows Vista AIK is still available here:

https://www.microsof...s.aspx?id=10333

but I am not so sure that there are projects still maintained that can use that as source, in case the Windows 7 AIK would be advised:

https://www.microsof...ls.aspx?id=5753

 

If you prefer, what most of the people on forums like reboot.pro are looking for is a "generic" and "wide" PE capable of doing "everything" and run "everything", while your *need* is much more "vertical", you need an environment which can be used to run DriveImageXML to restore an image (and that's it).

 

So, for a "general" tool there may be preferences by each person previous knowledge of the base OS (and people familiar with Dos/Windows may have some initial difficulties with Linux, and viceversa people familiar with Linux/*nix may have some initial difficulties with a Windows based PE) but in a very "vertical" use such as yours none of this will apply. 

 

:duff:

Wonko



#593 Rinxero

Rinxero
  • Members
  • 5 posts
  •  
    France

Posted 09 January 2018 - 09:58 PM

Hello Wonko,

Firstly Happy new year to you and so grateful for the extremely useful explanations you gave me in your previous post.

 

Apologies to have been so long in answering  as I left my desk and Computer for relaxing holidays...far away.

 

I hope that you had a happy end of te year.

 

With all your explanations I have made further progresses:

 

1) I managed to download and burned a CD-R with the Linux RuntimeLiveCd.iso  that means that irrespective on my success on Winbuilder , i will be able ( hopefully as i didnt try yet) to boot with the Linux RuntimeLiveCd.iso and restore  my driveimage. XML .

2) Now thanks to your explanations , i measured the importance of backing up the Master Boot Record (MBR).

But i am stucked there as the HdHacker.exe  file from Dimio is reported as a malicious  program (https://www.reverse....vironmentId=100).

In particular when i dowloaded HdHacker from the dimio mentioned site, my Bitdefender doesnt let me execute the exe file stating that it is infected and launching a cleansing procedure.

2 Questions if you confirm that HdHacker is not malicious,  
A) what evidence have you that this file  is clean and how do you explain the defense procedure of Bitdefender? ( Ratings by malwaretips users , press articles on Dimio ...)
How can i circumvent Bitdefender that prevent me to execute it?
B) If you confirm as evidenced tat HdHacker.exe is malicious would you have an other MBR Backup program that you know is clean.
 
Many thanks for your answer.
Best regards,
Rinxero


#594 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 10 January 2018 - 09:20 AM

Ah well, from time to time (and here and there) this or that Antivirus through its auto-magic-hyper-smart-mega-trans-heuristic technology will flag this (or that, or that other) file as malware.

 

No way to know if it is accurate or not (it is not in this case) but of course you shouldn't EVER trust blindly what a perfect stranger tells you on the internet.

 

BTW the file you submitted to www.reverse.it is not the actual HDhacker, but a (stupid) "portable version" you got from somewhere else (which anyway is possibly clean). 

 

In this case "stupid" because hdhacker is already portable, as a mattter of fact, if you are OK with the English interface you can run it as is from within the .zip file.

 

At least according to Virus Total, the actual hdhacker is clean (specifically for BitDefender):

https://www.virustot...sis/1515575464/

 

But there are tens of tools capable of just backing up the MBR, command line or GUI.

 

Personally I use dsfo, part of the DSFOK toolkit:

http://members.ozema...ware/index.html

*like*:

dsfo \\.\Physicladriven 0 512 C:\mynicembr.bin

Or -still say - *any* dd-like tool, after all it is just a matter of copying to file the first sector of your hard disk, you could use Clonedisk (as a cannon to shoot a fly ;)) if you want a GUI one or MBRWizard or MBRFIX, optionally with a GUI overlay, such as the good :dubbio: ol' pseudo GUI by jaclaz ;):

http://jaclaz.altervista.org/

http://jaclaz.alterv...X/mbrfix0.2.zip

(though I have no idea if the stuff still runs on post-XP systems)

or the (much better) one by Triton, that you can find here:

http://www.anwald.com/bartpe.html

http://www.anwald.com/coolXPE/umbr.rar

 

 

 

:duff:

Wonko



#595 Rinxero

Rinxero
  • Members
  • 5 posts
  •  
    France

Posted 11 January 2018 - 02:45 AM

Hello Wonko,

Still very grateful ‎.

I believe you!

Nevertheless what do you think about tis analysis:

https://www.hybrid-a...vironmentId=100

 

Now ‎when you write "you can run it as is from within the .zip file." what do you mean as I actually downloaded the hdhacker.exe from the dimio site you provided me. After downloaded on my c: drive when I execute the file, bitdefender block it. So how do you do?

Concerning the vistape.winbuilder.net ‎ after having downloaded the winbuilder083 , when I try to download the appropriate files checked as per "the terabyte" recommandation,

vistape_ss02.png

 

the winbuilder claims that it cannot connect to the internet(that is wrong as I am connected). I could enter some proxy /port/ connexion details on some map that winbuilder shows what do you advise.      

            Many thanks,Rinxero

 

 

 

 

 

     



#596 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 11 January 2018 - 11:02 AM

The file you submitted to:

https://www.reverse.it/

is HDHackerPortable_1.6.5.paf.exe, downloaded from:

http://download3.por...e_1.6.5.paf.exe

It is possible that the whatever modifications needed to create out of Hdhacker.exe the "portable" version HDHackerPortable_1.6.5.paf.exe triggers this (or that) antivirus.

 

The actual hdhacker file is a .zip, downloaded from here (and NOT from anywhere else):

http://dimiodati.alt...ip/hdhacker.zip

 

The actual hdhacker.exe (again the "original", "untouched" one from inside the hdhacker.zip file downloaded on the home page, and not from anywhere else) submitted to Virus Total, shows no issues in Bit Defender. (though it tests "positive" on a few other engines):

 

Baidu
Cylance
Symantec
TrendMicro-HouseCall
Webroot

 

 

Making a "portable file" for an ALREADY portable application makes no sense whatsoever.

 

The executable reads a few values from Registry (like - say - 72.18% of stupid GUI programs written and compiled with the stupid Microsoft compilers and libraries).

 

As said, it is entirely your responsibility to trust or not trust an antivirus, in any case alternatives has been given.

 

About Winbuilder and internet connection, it is flawed by design.

 

Winbuilder  is (should be) ONLY  a command processor, it should need not to connect to *anything*, and of course usually the settings are not working, the list of urls is outdated, or they are not working anymore (or both).

 

It is of course not at all your fault :), sorry if I seem grumpier :w00t: :ph34r: than usual , it is a long standing (actually from day one of Winbuilder) issue.

 

It could be however a connection issue, see here:

http://reboot.pro/to...o-be-connected/

http://reboot.pro/to...-077-rc2/page-3

 

:duff:

Wonko







Also tagged with one or more of these keywords: win7pe, vistape, multiboot, pe3, livecd, pe2, pe1

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users