ATIH2020 Boot Media boot issues

This sounds like you are creating and using the Linux rescue media.  Instead of using the simple method, go to advanced and see if it will let you create WinRE media.  

Normally, if you have a WORKING windows recovery environment, the simple method would build WinRE rescue media with it in 2018 to present, but will fail back to Linux if it is not found or if it is corrupted.  So try it manually and see if it can build it or not.  This should give your rescue media much better driver support for boot-ability.

I haven't had any issues booting the WinRE and/or WinPE on any of the systems I've tested it with (from ATI 2020 beta 1, 2, public release 1 and the public release 2 that came out today).  However, I am having issues getting the 2 public releases to complete a backup offline on one of my machine and have an open support case and thread for it.

Hi Bobbo, to my shame I didn't follow up, and even more stupidly I continued making system drive .tibx backups since this post even though I can't restore them without being able to boot to 2020 boot media!  (Just now I used the 2018 boot media to create a .tib Full backup, so I'm covered again!)(I didn't learn of the new .tibx format until after I found out I couldn't boot to 2020 media.)

While creating the WinRE media using the Advanced option I get lots of error messages that it can't load the drivers, and then when I try to boot the it I get the same result.  Maybe the problem is the structure of the driver folder I pointed it to?  

(That folder contains sub-folders that contain the drivers for the PC.  I used DriverBackup! to create the folder, and it worked perfectly to customise one of Ganfalf's WinPE .iso's.  Advice please?  I've only had that one experience successfully injecting drivers into an iso, I'm a noob at doing so.  I wish that [like Ghost did] ATI would grab the drivers by itself!  My personal history creating my own custom WinPE ISO's is strewn with humiliating failure.)

Coyote, I would suggest taking a different approach here.

If the older ATI 2018 Linux based rescue media worked OK for you with your computers, then try creating the same type of media with ATI 2020.  You can do this easily by taking the Advanced option then selecting Linux as the media type (not Windows PE).

Test with that media and see if the boot issue is resolved?

The alternative approach is to create the MVP Custom WinPE media but create this initially without adding any extra device drivers etc.  This is my preferred rescue media and the one that I have been using for several years now since Paul & Rob worked with the MVP's to put this together and iron out any early issues.

The main points about the MVP media is to simply unzip the MVP_ATIPEBuilder_v186 folder to the root of one of your drives, then to ensure you use 'Run as Administrator' when launching the main application within that folder, then just follow the prompts shown.

@coyote,

While creating the WinRE media using the Advanced option I get lots of error messages that it can't load the drivers, and then when I try to boot the it I get the same result.  Maybe the problem is the structure of the driver folder I pointed it to?  

I believe your thinking about this problem being caused by driver folder structure is indeed the issue.

"libpng warning: iCCP: Known incorrect sRGP profile"

The above error is likely an issue with the ICCP chunk that libpng checks for a PNG file.  It can be ignored.  there is more HERE

Does your Windows 8.1 machine boot using UEFI?  If yes your problem with booting may be that your boot order is incorrect so the bios is not reading or cannot locate the correct boot file.

Thank you both for following my link over here!

(I've got 3 months of system drive images I'd love to be able to restore.)

@Steve
I made the Advanced|Linux media type, and I got to the Menu, selected Acronis (I wish it were it's own default on that Menu, that it's not drives me crazy while I hover poised to select it), got past the blue Acronis screen, then got a blackscreen at first with a flashing cursor then it just hangs blackscreen.

As soon as I can (hopefully tomorrow) I'll try the MVP Custom WinPE media approach for which I just downloaded MVP_ATIPEBuilder_v186_Signed.zip

@Enchantech
"driver folder structure is indeed the issue"

I looked at the URL in your .sig but I didn't see the answer so I'll say:  I selected a folder containing only separate subfolders for each of the drivers to be injected.  Does that sound wrong?  (Can you direct me towards info on the right way to structure the driver folder?  Or alternatively to a program that automatically gathers Windows drivers into the proper folder structure?)

"Does your Windows 8.1 machine boot using UEFI?"

No.  Both my computers are ca. 2004, so they aren't UEFI.

@coyote,

As for the driver folder structure, I believe that the files you need are nested to deep in the structure for the tool to pick them up and add them.  They really should be extracted from the Windows driver repository. Since you used DriverBackup to extract the drivers I would copy them to the root of a flash drive if possible and point the Media Builder tool to that.  It should pick them up that way.

Your Win 7 PC boots Okay from the Linux media except for the issue with selecting the TI app once it loads correct?

Your Win 8.1 PC will not boot the Linux media.  This sounds like either the CD drive is not first in the boot order to boot from or, the Linux media lacks enough driver support for the PC and my guess is if that is the case it is a storage driver that is crashing it.

So try to build the WinRE media again on the 8.1 PC.  If you have not tried the Simple version you might want to as the tool will bring over the essential drivers needed for boot from the Windows repository.

If you're building WinRE, there really shouldn't be a need to add all those drivers. WinRE should include local system drivers. The main thing is making sure your WinRE or ADK matches the driver versions... I.e. if your WinRE is win7 but your driver's dri Win10... That's a no go.

In most cases Win10 WinRE should have all the drivers you need out of the box. If some are missing, just add those to start... Usually the ones that can be a problem are NIC, RAID and in some cases, USB controllers. I would just try the basic WinRE without extras drivers and see how it goes... Use the advanced option and then specifically choose WinRE. Then see how it goes.

First, I assure everyone that I know how to boot to a CD (I use the boot menu and Press Any Key if re bested), and have been doing so for decades including with the ATI boot media.

Second, it occurs to me I ought to have mentioned that this computer will not run Win10, not even a Win10PE.  It tops out at Win8.1.

Hi Bobbo, thank you!  I did try the simple WinRE, it wouldn't boot.

I'm most puzzled why I have no issues with the ATI2018 but this PC can't boot the Linux2020.

I tried the MVP_ATIPEBuilder_v186, it wouldn't boot.

Then I re-tried the Acronis media builder WinPE with all the drivers in one folder (that seemed to help, some appeared in the window), but it wouldn't boot.

Speaking of the all-drivers-in-one-folder, I just dumped all of the subfolders into one big folder that ended up with 157 files:

98   .dll
14   .inf
14   .exe
11   .cat
11   .sys
 2   .icm
 2   .dat
 1   .bit
 1   .cpm
 1   .nvu
 1   .pb
 1   .txt

(Er, I guess this has driven me crazy to create that table.)

@Enchantech
"Your Win 7 PC boots Okay from the Linux media except for the issue with selecting the TI app once it loads correct?"

Yes.

"If you have not tried the Simple version"

I did try it, no joy.

@coyote,

Sorry to hear that you have not had any success with this. It is strange that you cannot seem to make this work.  Given all you have said I can only guess that possibly having that huge overwhelming amount of drivers was to much.  How large are the total 157 files?

In general terms driver injection in bootable media only needs to have access to the .inf file of the driver package.  If other files within the driver package are required they will be extracted by the DISM tool which performs the injection of the drivers.

I suggest that you trim down the drivers to Storage Controller, USB Controller, and NIC drivers.  Only add those devices .inf files to the injection of the media and see if that will get it working.  Other than that I am out of ideas.

Second, it occurs to me I ought to have mentioned that this computer will not run Win10, not even a Win10PE.  It tops out at Win8.1.

What type of laptop is this?  There should be no issue running Windows 10 on a system running 8.1.  It may not be fully supported by the manufacturer, but the base drivers are very similar as Windows 8.1 and 10 are both concerned by Microsoft as "modern OS".   A good test would be to pull the main drive and pop in an old one (or a spare new one) and try a fresh Windows 10 install.  Honestly, can't see why Windows 10 would not install if Windows 8.1 can

Hi Bobbo, thank you!  I did try the simple WinRE, it wouldn't boot.

And did you try to do the Advanced option and WinRE as well?  They should be the same, but would be good to confirm if it successfully creates the rescue media, or not as WinRE.  The simple method defaults to Linux if it can't find or use WinRE.  What's on the rescue media when it's done?  Is there a "source" folder on the root with boot.wim in it?

I'm most puzzled why I have no issues with the ATI2018 but this PC can't boot the Linux2020.

Unfortunately, the kernel version of Linux gets updated from time to time and the kernel has base drivers built into it already.  Newer versions may have different drivers where older ones get removed for the new one and so the behavior can change.  We've seen it a few times now where things like a previously working usb 3.1 controller was working with an older version, but then stopped working when a newer version came out because the driver change no longer supported that card!  

I would stick with trying WinRE still and forget adding in extra drivers for the time being.  There may be something else preventing from booting... I know you know how to boot a CD/DVD, but this could be a bios setting... your system may be booting the older linux version in legacy mode, but trying to boot the WinPE/WinRE in UEFI mode (or vice versa).  You may need to disable secure boot, enable CSM\legacy in the bios, or try to use your one time boot menu to specifically choose the right boot method.  

If possible, test on another machine too. 

I've now tried more Acronis 2020 WinPE discs using Advanced to add a driver folder these 3 ways:

1.  Only the .inf files,
2.  Only the limited set of .inf files for "Storage Controller, USB Controller, and NIC drivers", and 
3.  The entire System32 folder for the OS (that took a while and at 1.1GB needed a DVDR to burn it).

None would boot.

Anyway, I appreciate the help everyone; bootable discs like WinPE are not something I'm good at.

"How large are the total 157 files?"

Oh, this is embarrassing:  331MB

@Bobbo
Both my computers are ca. 2004 (so the BIOS has no idea what UEFI is).  My other desktop can't even be upgraded from Win7.

As for the Win8.1 computer, Microsoft left the CPU behind for 64-bit on Win8
(that is, it can't even run 64-bit Win8.1).  Others had success getting Athlon 64 X2 and my chipset to 32-bit Win10, so it is a bit of a mystery why I couldn't, but I tried every trick in the book and devoted months and just couldn't.

"And did you try to do the Advanced option and WinRE as well?"

Yes, I tried a bunch of times with and without various drivers in the folder.

"What's on the rescue media when it's done?"

"Is there a "source" folder on the root with boot.wim in it?"
Yes.

My other PC boots the ATI2020 media with no issue.

Coyote, what type of computer is your problem 2004 machine?  What make of PC or motherboard?

I have some very old kit in my office, mostly waiting for me to take for recycling, all of which is incapable of running beyond Windows 7, including some with non-PAE processors.

I suspect that using the Linux version of rescue media will be the way to go here - it was for me with an old IBM T42 non-PAE laptop where IIRC I was able to use ATI 2019 rescue media with Linux and start options set for 'forcepae' when I last played with it some months back.

I concur with Steve on this.  We do not often see posts from users with hardware as old as yours so our thought process is unfortunately geared toward more modern hardware.  This means a lot of what we suggest simply doesn't apply.

Compaq Presario SR1913WM
ASUSTek NAGAMI2L 2.0
AMD Athlon 64 X2 2.4 GHz Dual Core 4800+

Just in case I created another Linux using the ATI2020 program's Advanced option:  Once again it fails just as reported above ("got past the blue Acronis screen, then got a blackscreen at first with a flashing cursor then it just hangs blackscreen").

Thank you very much, friends!

How long have you waited for the application to load at the blinking cursor?  It could take several minutes for the application to load and appear of screen.

EDIT: How mush RAM do your machines have installed?  Less RAM equals slower load times and I am unsure of what minimum requirements are at this point.  If your machines are 2GB or under I would say your questionable and that could be why the WinPE would not work also.  Issue here is that the application load entirely in RAM to run when using boot media.

Coyote, when creating the ATI 2020 Linux media, have you tried setting any of the Startup parameters that are available? 

Ditto to Bob's question about how long you have waited?  I know that on my older hardware boot seems to take an age, especially compared with more modern boxes!

Just created the Linux ATI 2020 media on a USB 2.0 2GB stick using just defaults then used this to boot a very old home-brew ATX P4 system (2GB memory) and it took over 7 minutes to get to the main ATI graphic application screen.

The ATX system is running on an ASUStek P4P800-VM motherboard and cannot go higher than Windows 7 32-bit which it is running along with World Community Grid software for worldwide grid computing for finding cures for lots of different diseases etc.

I concur with Steve on his example.  I also would say that if RAM is less than 2GB the media might not load at all.

I haven't timed the wait-times, so I'll try it again and report back.  (I'm guessing I've waited an average of 20 minutes.  On my even slower other machine it just takes a couple minutes to boot of which I recall no extended blackscreen period.)

Both machines have 4GB RAM.

"have you tried setting any of the Startup parameters that are available?"

No, but I just read the Help page "Acronis bootable media startup parameters".  Any suggestions on which to try?

The only startup parameter I have used is not even documented in the user guide (forcepae), so would be a case of trial & error to see if any parameters make a difference?

acpi=off is your best bet for hardware compatibility.

OK, I re-ran and times the ATI 2020 Linux boot media with and without the parameter acpi=off

Without the parameter it exactly as before got the the blackscreen and hung there for 3 hours 35 minutes until I terminated the test.

With the acpi=off parameter I terminated the test after 1 hour 42 minutes; the cursor screen never went black, the flashing cursor persisted, at first with just lines 1 and 2 showing:

do_IRQ: 1.55 No irq handler for vector

Loading, please wait...

Then after 25 minutes a new line 3 appeared (pushing the flashing cursor to line 5):

ERROR: asr: reading /dev/sda[Input/output error]

Then 5 minutes later another new line appeared:

ERROR:  ddf1: reading /dev/sda[Input/output error]

Then a duplicate line 4 minutes later:

ERROR:  ddf1: reading /dev/sda[Input/output error]

Then 4 minutes later:

ERROR:  hpt37x: reading /dev/sda[Input/output error]

Then 2 minutes later:

ERROR:  hpt45x: reading /dev/sda[Input/output error]

Then 3 minutes later:

ERROR:  isw: reading /dev/sda[Input/output error]

Then a duplicate line a few minutes later:  

ERROR:  isw: reading /dev/sda[Input/output error]

Then a duplicate line a few minutes later:  
ERROR:  isw: reading /dev/sda[Input/output error]

Then, gradually as above:

ERROR:  jsmicron: reading /dev/sda[Input/output error]  

ERROR:  lsi: reading /dev/sda[Input/output error]

ERROR:  lsiv2: reading /dev/sda[Input/output error]     <at the one hour mark>

ERROR:  nvidia: reading /dev/sda[Input/output error]    

ERROR:  pdc: reading /dev/sda[Input/output error]  

ERROR:  pdc: reading /dev/sda[Input/output error]  

ERROR:  pdc: reading /dev/sda[Input/output error]  
ERROR:  pdc: reading /dev/sda[Input/output error]  

ERROR:  pdc: reading /dev/sda[Input/output error]  
ERROR:  pdc: reading /dev/sda[Input/output error]  
ERROR:  pdc: reading /dev/sda[Input/output error]  

ERROR:  pdc: reading /dev/sda[Input/output error]

ERROR:  pdc: reading /dev/sda[Input/output error]  <test terminated>

Well, looks to me like the Linux kernel in the media lacks driver support for your JSMicron hard drive controller (the dev/sda errors).  Are your drives SATA?

You might do a google search using your JSMicron controller model name and some of your errors like do_IRQ: 1.55 No irq handler for vector  etc. and see what turns up. 

You might also try the pci=biosirq in the startup command.

Thanks Enchantech!

My HDDs are all SATA.

I've thoroughly failed to find what brand hard drive controller my mobo has, let alone it's model.  And my SATA card [SIIG SC-SA4011-S2] uses Silicon Image.

Googling errors led to a lot of threads but I didn't find anything that seemed relevant.

I tried pci=biosirq but just blackscreen.

I tried nousb, just blackscreen.

@coyote,

So, to find your controller model open Control Panel, look for Device Manager and open it, look for Storage Controllers, click on the > to the left of Storage Controllers to expand it.  Locate the JMicron entry, right click on that entry a select Properties. On the General tab you will see the name and hopefully the model number of the device.  If the model number does not show there click on the Driver tab and make note of the Driver Date and Driver Version number.  Post those here.