MVP Tool - CUSTOM ATI WINPE BUILDER
Patrick,
Glad you got it working.
We knew that about mapping a drive with the net use command. See Map.cmd and Map.cmd.bak in the MappedDrive folder. The build is paused when you select the option to map a network share. At that point you see instructions to edit Map.cmd to enter your USERNAME and PASSWORD.
... The build is paused when you select the option to map a network share. At that point you see instructions to edit Map.cmd to enter your USERNAME and PASSWORD.
I saw that but didn't understand that the username and password had to be included even when they were not appropriate - for a public share that doesn't have a username and password.
Good point. It just seems to be needed to initialize the process.
Another puzzlement. While I have added my wireless profiles and can manually add them an connect with them, I cannot get this done automatically. I've put my profiles in the Wifi folder. The build lists the profiles it sees and adds them with the Wifi interface id as part of the file name so I actually have two copies of the profiles. And I've modified Wifi.cmd to use my profiles:
echo.
netsh wlan add profile filename="X:\Program Files\Wifi\Profiles\Okeefeler0000.xml"
netsh wlan add profile filename="X:\Program Files\Wifi\Profiles\Okeefeler0002.xml"
ping -n 10 127.0.0.1 > nul
netsh wlan connect name=Okeefeler0002
echo.
But when I boot the recovery medium it says a file cannot be found (without saying what file) and then makes referece to "Your_ssid" as though I had not changed Wifi.cmd. (Or Wifi.cmd.bak was being used.) And when I look at the contents of Wifi.cmd my changes are, in fact, not there. That makes me think I'm changing the wrong copy of Wifi.cmd, but the one I'm changing is in the same directory as the Profiles folder that the build process changes.
Any idea what might be going on?
wifi.cmd should remain in the folder before the profiles folder. this will get copied to Windows\System32 in the WinPE and is being launched from there. If you moved wifi.cmd into your profiles folder, it won't get copied into the WinPE so that is probably what happened (at least that is what it sounds like)
wifi.cmd.bak is just an extra "original" template you can use in case you mess something up and want to restore the original to work with again.
Oops. I reported the problem incorrectly. I brought up the recovery medium to double check and found that the Wifi.cmd does have my changes in it. But it is not the one being executed. I'm not aware that I moved it. (It's not in the Profiles folder. IT's in the Wifi directory that contains the Profiles folder.) But the comments in the .cmd file says it should be in X:\Program Files\Wifi\, not X:\ Windows\System32. Is that wrong?
When you build with wifi, the initial profiles do go to X:\program files\wifi\profiles - sounds like those are there.
However, the WinPE is launching the emedded wifi profiles that you include during the build with X:\Windows\System32\wifi.cmd - double check to see what's in that file as that is what it is trying to load automatically for you.
The add wireless profile.cmd or exe in X:\program files\wifi (and shortcuts to it in the start menu) are for additional / manual entries... let's say you have another wireless profile that you didn't add to the build, but want to connect. You can then add those profiles manually with those.
The YOUR_SSID should be the name of the actual SSID name you would see from the router.
netsh wlan add profile filename="X:\Program Files\Wifi\Profiles\YOUR_SSID_PROFILE.xml"
ping -n 10 127.0.0.1 > nul
netsh wlan connect name=YOUR_SSID
Then, open up your 0002.xml profile with notepad and double check that the SSID is the same one you're putting for "your_ssid", to be sure.
<?xml version="1.0"?>
<WLANProfile xmlns="http://www.microsoft.com/networking/WLAN/profile/v1">
<name>YOUR_SSID</name>
<SSIDConfig>
<SSID>
<hex>XXXXXXXXXXXXX</hex>
<name>YOUR_SSID</name>
</SSID>
All the ssids in X:\program files\wifi\ are correct. Manually executing X:\program files\wifi\ Wifi.cmd adds the profiles and connects. I guess I'd better boot up WinPE and see what's in X:\Windows\System32\wifi.cmd. Or maybe I should learn how to mount it with DISM. That would be a lot faster than rebooting all the time to check this.
By the way the profile files built by the builder have names like "Wi-Fi 2-Okeefeler0002.xml" which seem to be interface name followed by profile name. Should I be entering that name when the builder prompts me for the SSID?
No, use the SSID name. The profile name is created by Microsfot when you export it. You can manually run teh command from an elevated command prompt
netsh wlan export profile name="%SSID%" folder="%SRC%\WiFi\Profiles" key=clear (replace %SSID% with your actual SSID name and %SRC% with the path you want to copy it too.
If you want to mount the boot.wim, to manually modify or view files in you you can use DISMGUI to help make the process a little easier.
Instructions... http://www.thewindowsclub.com/dism-gui-windows
Alternatively, if you just want to see what's in it, you can open boot.wim with 7zip and copy files out of it for easy access. You can't modify, but makes it easy to view and poke around.
Patrick,
The netsh wlan add profiles line should have the name of the profile as it appears in the Profiles folder. The netsh wlan connect line should be just the ssid.
Hers's how the lines look in my wifi.cmd file:
echo.
netsh wlan add profile filename="X:\Program Files\Wifi\Profiles\Wi-Fi 3-NETGEAR53-5G.xml"
ping -n 10 127.0.0.1 > nul
netsh wlan connect name=NETGEAR53-5G
echo.
What are the names of the profile xml files in the Profiles folder?
Also, don't add two profiles in WiFi.cmd. Only add the faster profile. My computer also has two profiles. One for the 2.4G and one for the 5G network. I only want to add the profile for the faster (5G) network.
Patrick,
The netsh wlan add profiles line should have the name of the profile as it appears in the Profiles folder. The netsh wlan connect line should be just the ssid.
Hers's how the lines look in my wifi.cmd file:
echo.
netsh wlan add profile filename="X:\Program Files\Wifi\Profiles\Wi-Fi 3-NETGEAR53-5G.xml"
ping -n 10 127.0.0.1 > nul
netsh wlan connect name=NETGEAR53-5G
echo.What are the names of the profile xml files in the Profiles folder?
Yes, I understand all that (unless I misunderstood you). My profiles are names pokeefeler0000.xml and pokeefe0002.xml. (Yes, there was a 0001 at one time.) But the build process added one named "Wi-Fi 2-Okeefeler0002.xml" (which I think related to my having multiple USB wireless adapters plugged in). The build process asked me to enter an SSID if I haven't already specified one. I gave one. Is that when it builds the extra profile file?
Also, don't add two profiles in WiFi.cmd. Only add the faster profile. My computer also has two profiles. One for the 2.4G and one for the 5G network. I only want to add the profile for the faster (5G) network.
Hmm. That means I have to give up on my idea to have just one recovery device for my 3 computers (since one of my USB wireless adapters supports only 2.4G) but I think I'm giving up on that idea anyway. I think I'm having trouble getting all the right drivers so maybe I'll just build a separate USB flash drive for each and not bother with any custom drivers.
I've also decided to exclude NAS drive mapping out of the process. It's a pain waiting that 60 second pause knowing the mapping is going to fail anyway because the network setup failed. I'm now manually copying a .cmd file to flash drive after the build process is done, but would it work to put the mapping .cmd file in the "Extra" folder? All I need is an easily found .cmd file that I can execute after the WinPE system has initialized.
By the way, on one of my computers I'm pretty sure I had to wait more than 60 seconds. I've taken to just issuing an IPCONFIG command evey once in a while. Once it shows an actual configuration I know I can map the drives.
Yes, the extra folder should be just fine. You could even just put it on the root of your flash drive if you wanted and navigate to it and launch it from there. The 60 seconds is a long wait. I prefer to just map the drive manually myself as well, but we're trying to give everyone some different options based on preferences.
Is it possible to access the unix / linux / ubuntu shell from the advance bootable media?
If so, how?
It would be great if I could access the *nix shell so I couldd perform " dd " commands to clone my system since it already has drivers and a bunch of other features.
If that feature is not available, from the advance bootable media, please consider adding it.
Thanks
I successfully created the advance bootable media and successfully backed up my Dell XPS 15 9550 4K Screen
I then used same media on my 9530 and while all the menus and resolution was ok, once I started backup the window it opened was so small I could barely see anything, see attached file.
I tried to change the resolution using the utility setres that comes with the bootable media; however, it said the operating system ( windows 10 pro 1607 ) rejected it.
Any advice.
I cannot see progress or anything. I just played with pressing tabs and didn't cancel and also selected "Shutdown" when finished.
I see the external destination ( disk ) LED rapidly blinking so I suspect it's transfering data. I'll give it couple of hours 3 max to see if it completes backup and shuts laptop down.
I believe I have couple more years on my subscription, but I was wondering, once we create the Advance Bootable Media will we need a valid license to use it in the future?
I have valid license / subscription now, but will I need a valid license / subscription in the future once the license / subscription expires?
Is a license / subscription even needed to create and use the advance bootable media?
Is it lifetime access and use the the advance bootable media once it's been created?
Are incremental backups performed after a full backup truly faster?
In principle they should be because they are only backing up the difference / changes since the last backup.
However, does the software first go through the whole file sysrtem scanning what files are new or have been modified to create a list of items to backup or does it simply starting backing up and looking at attribute bits and dates to see what needs to be backed up?
I've always done full backups; however, if the incrementals are " 100% " reliable and are at least 50% faster ( takes 50% less time ), I'll start performing those on a more regular basis.
Also, when I say reliable, I mean can not only create the backup, but also successfully restore.
So those who have created and restored using Full, then incrementals, please let me know youre experiences, both good and bad.
I'd rather do Full Image backups because at least I know I've been able to restore " most " of the times; however, there have been several instances where I had at least five full backups, including sector to sectore among the five and not one of them worked; however, I was fortunate to have created a " dd " image backup. " dd " backups never failed when I tried to restore; howver, they are risky and easy to destory whole source drive if one isn't careful.
I should probabl script it in the future.
Is it better to perform full image backups or full with incrementals.
I don't have much confidence in Acronis software much nor support.
I'm grateful and appreciative for the forums they have created that allows us to reach out to others; however, had it not been for the main forum mentors on this thread who not only help and advise us but actually created software we couuld use, then Acronis software doesn't work.
I purchased 2014, 2016 and 2017 and none of their software ever worked on any of my Dell XPS PCIE NVMs because of missing drivers.
When I contacted them, they basically told me tough luck and wouldn't give me a refund, even though it was within 30 days...
SO again, thanks to those on this forum who have been instrumental in helping the world community at large...
SG - what resolution did you pick when you built the rescue media? You may want to try building it with 1920x1080 or even trying to set to the default size of 1024x768. WinPE resolution is dependent upon display drivers available in the WinPE. 4K monitors may still be a bit too advanced for basic winpe, so setting a lower resolution at build may help.
No, there is no LINUX option with the advanced tool. It is using Windows ADK only and is Windows based. This is a stripped down Preinstallation Environment (PE) provided by Microsoft in the ADK and has many limitations, but does have ability to be customized in many regards.
Incrementals only backup the changes since the last full or last incremental so can be time and size saving - considerabley. However, they are not infallable. Full backups are generally the safest, most reliable, but the slowest and largest. Think of it this way though...
Let's say you backup weekly doing only fulls and take 1 full a week. If you made a backup scheme with 1 full and daily incrementals each week, you get more backup recovery points. Assuming those incrementals are all good, you ahve more restore options with not much more space being used. You might be able to go 2 weeks before you feel the need to do another full. Incrementals, although they are generally reliable, are the LEAST reliable backup method because of their dependency not just on the original full, but each incremental that came before them. Personally, I prefer differentials. They work similarly, but each differential is only reliant on the original full in that chain and nothing else. They are bigger than incrementals, but have less dependency on other backup files and still smaller than a full.
In my setup, I take a weekly full and diffs every other day. I keep 3 weeks of backups (3 chains which include 1 full and 3 diffs in each chain). This gives me pretty recent restore points and don't take up much space until the next full is run.
Bobbo,
All laptops have 4K touch screen.
Media was built on the 9550;
9550 4k Touch Screen : everything looked fine, all windows and screens looked ok
9530 4K Touch Screen : everything looked fine, except the one window I zipped in previous post
Not sure what resolution I picked, but fact that everything was ok on the 9550 and most of the screens were ok on the 9530 except that one screen suggest it may be something else.
For the moment I'm ok; however, I'll investigate a bit more next time I use it.
Bottom Line is thanks for creating the advance media and sharing it with the rest of us.
Although I haven't tried it yet, I'm thinking of using VMWare Workstation to setup some windows platforms and test the advance MVP bootable media. That way there's absolutely no risk if things misbehave.
Can't think of any reason why it shouldn't work, but I'll see later...
Can't hurt. When you build VM's, they have a set bios mode though - UEFI or Legacy that should be configured before the OS is installed and will only give you one boot option to match. You can switch the bios mode fo the VM, but then the installed OS wont' be bootable.
Just built and tested the latest MVP WinPE builder 11.1. No issues with the build and it loaded very quickly compared to the previous build I had (9.9). Another excellent job by the MVP team.
Thanks for the nice feedback! Mustang and I are always trying to make improvements where feasible.
After been unable to make Acronis backups of my DELL XPS15 9550 laptop (WIN 10 Home X64) using original Acronis 2016, I made a MVP ATIPE USB stick at the end of 2016 using the Basic 5.9 version.
This USB stick worked with above DELL OK and some backups were made.
Since then I made the proposed by DELL updates, but NO any DELL BIOS update, as well WIN10 OS updated automatically.
Lately I try to make a new Acronis backup using the above USB stick, but the booting procedure stop just on first splash screen.
I have same responce also with the (simple-with no extra drivers) WINPE USB stick, made from Acronis CD.
Other bootable USB sticks, like Ubuntu or WINDOWS recovery one, are booting OK...
I also updated afterwards to latest DELL BIOS but no any change.
Any advice, please??
I would suggest creating a new Bootable USB using the Advance MVP tool.and see how that works.
If the advance doesn't work it has better logs to help isolate the problem..
I suspect the new MVP tool will work
Thanks advice SG...
I will try it soon.
"file creation error - the parameter is incorrect"
I have just installed ATI 2017 on two machines: Dell XPS15-9560 laptop running Windows 10 PRO and a Dell XPS9100 desktop running Windows 7 Ultimate. Had absolutely no problelm with MVP WinPE Builder on the laptop. On the desktop I could not make the bootable media on any one of a number of USB thumb drives. MVP WinPE Builder gave me the above error after it attempted to write the ISO to the drive. I was successful in building the bootable media on a DVD so I do have a working situation. On the other hand I would like to understand and fix the USB drive issue for the future.
Is this a known issue?
Suggestions:
1. Make sure Windows Disk Management lists the USB drive as "Removeable".
2. Do a "Full" format of the USB drive as FAT32.
3. Try using the USB drive that was successful on the laptop.
One question: After the "Full" format does it matter whether I say Y or N when MVP WinPE Builder asks if I want to format the USB drive?
Ken, if you have done a full format then you can take either option when MVP asks.
You must say YES. If you say NO, the utility will exit without writing to the USB drive. The NO option gives you a way to stop writing to the USB drive if you don't want to loose the existing data on the drive.
So, I followed the 3 suggestions made by Mustang above and still failed to create a USB bootable flashdrive on the Windows 7 desktop. As always getting the message "file creation error - the parameter is incorrect" at the point that the iso is to be written on the flash drive.
I then took a flash drive that had failed on the desktop machine and successfully created a bootable drive with the MVP ATIPEBuilder on the Windows 10 laptop with no errors.
I did a search in a Microsoft Forum on "file creation error - the parameter is incorrect" and found this:
-
"The problem lies with the MakeWinPEMedia.cmd
After the script partitions and reformats the flash drive, the disk appears offline for about 10 seconds (can be verified if you have Explorer open). This for some reason messes up XCOPY in the way the command is written.
SOLUTION:
Open MakeWinPEMedia.cmd using notepad (notepad "C:\Program Files\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\MakeWinPEMedia.cmd")
REPLACE:
xcopy /herky "%WORKINGDIR%\%TEMPL%" "%DEST%\" >NUL
WITH
xcopy /herky "%WORKINGDIR%\%TEMPL%\*.*" "%DEST%\*.*" >NUL
notice the \*.* at two places, thats what somehow makes XCOPY wait for the disk to be ready and then copies the files."
-
But this makes little sense to me. Perhaps it will ring a bell with one you experts. As for me I am still stuck in that I cannot make a USB bootable drive for my Windows 7 desktop.
-
By the way, I would be completely hosed without the MVP ATIPE Builder. Nice work!
-
Ken
This is exactly the problem why the USB bootable drive is not created.
About 3 years ago I had a similar problem when creating a bootable stick according this guide:
54130: Guide to building a 64 Bit UEFI Secure Boot WinPE 5.0 CD or USB Flash Drive running TIHome 2014 with or without Disk Director 12
https://forum.acronis.com/forum/54130
In post #16 I describe how to change MakeWinPEMedia.cmd:
-------------------------------------------------------------------------------------------------
The problem lies with the MakeWinPEMedia.cmd
After the script partitions and reformats the flash drive, the disk appears offline for about 10 seconds (can be verified if you have Explorer open). This for some reason messes up XCOPY in the way the command is written.
SOLUTION:
Open MakeWinPEMedia.cmd using notepad ( notepad "C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\MakeWinPEMedia.cmd" )
REPLACE:
xcopy /herky "%WORKINGDIR%\%TEMPL%" "%DEST%\" >NUL
WITH
xcopy /herky "%WORKINGDIR%\%TEMPL%\*.*" "%DEST%\*.*" >NUL
notice the \*.* at two places, thats what somehow makes XCOPY wait for the disk to be ready and then copies the files.
-------------------------------------------------------------------------------------------------
SV1DH,
What version of Windows 10 Update & Bios are you using.
In command window ( cmd.exe ) type: msinfo32; should get pop-up screen.
I'm running:
Windows 10 Pro
Version: 10.0.14393 Build 14393
BIOS Version/Date Dell Inc. 1.2.21, 2/17/2017
SMBIOS 2.8
BIOS Mode UEFI
SV1DH,
What version of Windows 10 Update & Bios are you using.
In command window ( cmd.exe ) type: msinfo32; should get pop-up screen.
I'm running:
Windows 10 Pro 1607
Version: 10.0.14393 Build 14393
BIOS Version/Date Dell Inc. 1.2.21, 2/17/2017
SMBIOS 2.8
BIOS Mode UEFI
Ken and Jan,
Thanks for bring that issue up. I'd forgotten about it as I never experienced it on my computers. I'll see about building the fix into the MVP script so you won't need to make the changes to MakeWinPEMedia.cmd manually.
EDIT:
It looks like the issue is fixed in the Windows 10 ADK's. The line appears as follows:
xcopy /herky "%WORKINGDIR%\%TEMPL%\*.*" "%DEST%\" >NUL
Note the *.* has only been changed in one place.
Ken,
What ADK are you using on the Windows 7 computer. I think the Windows 8 and 8.1 ADK's still have the problem. You can install a Windows 10 ADK on the Windows 7 computer and see if the issue is fixed. In the meantime, I'll see about having the MVP script modify MakeWinPEMedia.cmd automatically.
Mustang,
My version of ADK has a file version 8.100.26866.0. technical.microsoft.com says it is the correct version for 7, 8, 8.1, server 2012, and server 2012 R2.
There are now two version of windows 10 adk. One for Windows 10 version 1607 and one for the new 1703. On the microsoft developer site they claim you should install the version associated with your version of Windows 10. So, given these three versions of adk which one should I have installed on my windows 7 machine?
Also, I was just upgraded to 1703 on my windows 10 machine. Should I worry about changing the version of adk installed there as far as MVP ATIPEBuilder is concerned?
I look forward to the new version of the MVP script!
Ken
Ken,
Any version of the ADK should work on the Windows 7 or Windows 10 machines. I am still using the first of 4 Windows 10 ADK's on my 1703 Windows 10 computer.
Mustang,
Success! I installed ADK for Windows 10 1703 and that solved the problem. No longer getting the error message and the USB drive booted, found my hard drives and restored a file. So all is well.
Thank you,
Ken
Hi SG, sorry for delay to reply.
My DELL XPS15 9550 is running now:
WIN10 Home
Version: 10.0.14393 Build 14393 (which correspond to version 1607 for correct ADK selection, with which USB was originally build)
BIOS DELL 1.2.25 dated 5/7/2017 (the USB stick MVP basic 5.9 was working with V 1.2.19 but not anymore, not working with 1.2.25 either ..)
SMBIOS 2.8
BIOS Mode: UEFI
Any comments, please??
SV1DH,
I had problems with the basic.
I installed the advance 11.0. I think latest is 11.1 now. Try Advance it should work. It worked for me on both 9530 & 9550.
I've created system ( disk ) image backups only no restores...
SV1DH - did you try the ADK 1703 (most current ADK for Win10)?
Jan's post above is the fix, however, it is fixed by default in Win 10 ADK 1703 already. So, you can grab the latest ADK from Microsoft and use that instead, or you'll need to go to the following file and manually edit the existing version of it with notepad (copy it somewhere else so you maintain the original - just in case).
C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\MakeWinPEMedia.cmd
REPLACE:
xcopy /herky "%WORKINGDIR%\%TEMPL%" "%DEST%\" >NUL
WITH
xcopy /herky "%WORKINGDIR%\%TEMPL%\*.*" "%DEST%\" >NUL
I
Hi SG
I will try your advice, making AGAIN both basic and advanced versions, keeping fingers crossed...
Thanks anyway.
Hi Bobbo and thanks for advice.
My previous USB stick was made with 1607 ADK, since this version was the latest release on that time (Dec 16) for my windows version and worked perfectly for several months/backups, seeing OK the SSD of DELL XPS15 9550.
Then this stick is not booting anymore and stops on first splash screen (with the half cycles on lower part of screen).
BTW also the original (without the extra drivers) WINPE Acronis USB stick is not booting anymore.
Please let me know if I can use the latest 1703 ADK, although my win 10 version is still 1607, and if this no booting problem can be a digital signature one.
Hi guys,
the german blogger team Deskmodder is quite known in my country for their excellent content and tutorials around Windows 10.
Now they have released a tutorial how to integrate Disk Management console, Powershell and Secure Boot into Windows PE. I think this might be interesting for your valuaeable project. Especially the first one for those not so firm with usage of diskpart.
of course the article is in german, but Google Chrome should be able to insta translate it to an understandable level, most as the dism commands are universal.
https://www.deskmodder.de/wiki/index.php?title=PowerShell_in_Windows_PE…
-
One question is there a known incompatibility of Windows PE with high resolution displays? I have encountered a serious issue on 2 Dell convertibles where the native Windows PE built by ATIH results into very malformed windows where you can hardly use anything without rezising them. If you don't have seen this I will raise this to the Acronis support. It is pretty unuseable.
En réponse à SV1DH - par truwrikodrorow…
Hi
I build a new advanced 11.1 USB stick, installing and modifying first 1607 ADK per Ians comments (adding *.* on TWO points) and its working now, booting and reading DELLs (XPS15 9550) NVMe SSD OK.
Strange enough a new basic 5.9 USB is booting now OK, but its still not reading the above SSD.
Anyway my USB booting and reading SSD problem seems to be solved and like to thank all for advice...
Hello Guys Mvp Team :) Outstanding job . I did my Iso with your super useful utilty ,i was putting in the custom drivers folder i the Samsung Nvme Drivers ( .Cab , .Sys. , .inf ). No prob . All the drives are there now . In Raid mode . The only question is , when i'n m backing up from your Mvp boot Cd , i'f i'm asking the validation the Acronis Backup that i'm doing , the backup fails . If i'm not asking , it goes fine . So , as a matter of being sure of the backup , still i have to make the backup on Windows . I don' t know why this happens , but i wanted to share this with you , because maybe i did something wrong , and you can help me sort out . Thank you in advance , i hope you have a serene day , Michele
Michele,
I tested a backup with validation booted from the MVP Tool using TI 2018 Beta (I don't have TI 2017 installed anymore). The backup and validation completed without issue.
Did the backup fail before or after the validation portion started? You may want to run check disk on your drives to make sure they have no problems.
I did notice that the default option for backup method was set to incremental. I changed it to full before selecting the validation option. If you let it run with the default incremental option, please try again changing it to full. Other than that, I can't think of anything you could be doing wrong. It's possible the fault could be in the TI 2017 WinPE program.
En réponse à Another par truwrikodrorow…
Hi, I have been trying to locate Advanced MVP ATIPEBuilder version 9.6 program. I could not find it including Acronis MVP Google Drive. Please tell me exactly where I could download it. Thanks.
The older versions are here https://drive.google.com/drive/folders/0B8uZDIFmupY7a1ctaVpmM3duUHc