316 replies to this topic

[wimb]

• changeable size of second partition (default 40 Mb)
• changeable type of second partition (default FAT32 0C)
• option to format or not second partition (default format)

Certainly, it would be nice if Lancelot can test Make_USB.exe and
can determine if making a second partition on USB-stick is useful to him.

The program makes on demand an unformatted second partition and format is not a possible option as long as the stick is a removable device.
The nice thing is that you can define a second partition without having to install a filter driver.

The size and the type of the second partition can easily be modified by changing and running the AutoIt3 source code.
For this purpose Copy U_XP_SET\USB_XP_Setup\makebt\au3scr\sources_au3\Make_USB.au3 to your U_XP_SET\USB_XP_Setup folder.
And Change the Number of Cylinders parameter $NrC2=5 in Func _FormatUSB() at will (use e.g. $NrC2=1).
Similarly one can change the FileSystem of the second partition entry from 0C (=FAT32) in 0E (=FAT) or 07 (=NTFS) in

$partab_2 = "0000" & Hex($BSec_2, 2) & Hex($BCyl_2, 2) & "0C" & ........

But I think the first thing we need to know is whether the second partition as defined has any effect,
which question can simply be answered by making USB-sticks using Answer to make second partition is Yes or No.

[amalux]

Hi wimb

Sorry if dumb question but what am I doing wrong here?
 mbrbuerr.JPG   68.69KB   116 downloads

[wimb]

Could it be you are using Vista as OS.
In that case you need to switch User Account control Off

[amalux]

Could it be you are using Vista as OS.
In that case you need to switch User Account control Off

No, XP Pro SP2

[Lancelot]

Hi wimb

Sorry, i can not test, reason is i am using now Asus P5B board (old info about p5b fixed on online topic), my problem old pc is now at old home which can not be reached for a looong while (AsusP4P800) (during last 3 months i migrated a lot)
I can not test but I share online vision and trust his results (well i am an emotional man )

I did a couple of tests with 4gb kingston ufd, ntfs + fat32 , with yes yes yes, no no yes --> all bootable but as i wrote before, current pc dont have problem (ps: auto selected on bios)

Well i can not contribute with Make_USB.exe ufd perfect bootable tests, but i will ask others around.

I have couple of hostosx64 and gui request/support (no need x64 compiling)
but they can wait till your hard work finishes as they are out of subject for now, no need to break concentration.

ps: I am a close silent reader of this topic, sorry for late answer

[wimb]

No, XP Pro SP2

Hi amalux,

Unknown problem with MBR_Backup.cmd ....

Is there a MBR_%datum%_%compname%.log file in MBR_Backup folder ? Please give as attachment.

Is there a new folder MBR_%datum%_%compname% then if present please give MBR_%datum%_%compname%.txt file as attachment.

Don't know what occurs, have to study.

May be something with date or computername ?
What do you get in cmd window with: C:\>echo %DATE%
Are there spaces in %DATE% ? Should not be a problem.

Try to run PARTINFW.EXE in cmd window like:
C:\MBR_Backup\makebt>PARTINFW.EXE

Is there normal output with HD and Partition Table Info or is there an Error Message of PARTINFW.EXE ?

[wimb]

I did a couple of tests with 4gb kingston ufd, ntfs + fat32 , with yes yes yes, no no yes --> all bootable but as i wrote before, current pc dont have problem (ps: auto selected on bios)

Hi Lancelot,

Thanks for testing Make_USB.exe on new mobo ASUS P5B.
Good to know all made USB-sticks are bootable.

I have no doubt on results of online.
That is why the option of second partition was build in.
But it would be nice to have more experimental results and to find out what is the smallest second partition that has the desired effect.

[amalux]

Hi amalux,

Unknown problem with MBR_Backup.cmd ....

Is there a MBR_%datum%_%compname%.log file in MBR_Backup folder ? Please give as attachment.

Is there a new folder MBR_%datum%_%compname% then if present please give MBR_%datum%_%compname%.txt file as attachment.

Don't know what occurs, have to study.

May be something with date or computername ?
What do you get in cmd window with: C:\>echo %DATE%
Are there spaces in %DATE% ? Should not be a problem.

Try to run PARTINFW.EXE in cmd window like:
C:\MBR_Backup\makebt>PARTINFW.EXE

Is there normal output with HD and Partition Table Info or is there an Error Message of PARTINFW.EXE ?

Sorry, no txt or logs but here's cmd results:
C:\>echo %DATE%
Sat 05/02/2009

--
C:\MBR_Backup\makebt>PARTINFW.EXE

PARTINFW 1.11
Copyright © 1996-2008 TeraByte, Inc. All rights reserved.

Run date: 05/02/2009 4:02

====================================================================
MBR Partition Information (HD0 - 0x29D529D4)
(CHS: 1022/254/63) (WCHS: 14593/255/63)
+====+====+=============+====+=============+===========+===========+
| 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 29848707 |
| 1: | 0 | 1023 0 1 | 7 | 1023 254 63 | 29848770 | 29848770 |
| 2: | 0 | 1023 0 1 | 5 | 1023 254 63 | 59697540 | 172634490 |
+====+====+=============+====+=============+===========+===========+
Volume Information
+----+----+-------------+----+-------------+-----------+-----------+
| 0: | 0 | 1023 1 1 | 7 | 1023 254 63 | 63 | 172634427 |
| 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
MBR Partition Information (HD0) Continued:
+====+====+=============+====+=============+===========+===========+
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
+====+====+=============+====+=============+===========+===========+
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 63 Total Sectors: 29848707 ID: 0x1
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 63
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x01C77480
MFT LCN: 0x08EA23
MFT Mirr LCN: 0x0CB2FD
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x82C0513EC0513A1D
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 29848770 Total Sectors: 29848770 ID: 0x2
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 29848770
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x01C774C0
MFT LCN: 0x03
MFT Mirr LCN: 0x03FF
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x08E2FEE2A
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 59697603 Total Sectors: 172634427
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 63
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x0A4A3138
MFT LCN: 0x04
MFT Mirr LCN: 0x0400
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x13BE0F84F1495F1
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
====================================================================
MBR Partition Information (HD1 - 0x45058CFD)
(CHS: 1023/254/63) (WCHS: 60801/255/63)
+====+====+=============+====+=============+===========+===========+
| 0: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 1: | 80 | 1 0 1 | f | 1023 254 63 | 16065 | 976752000 |
+====+====+=============+====+=============+===========+===========+
Volume Information
+----+----+-------------+----+-------------+-----------+-----------+
| 0: | 0 | 1 1 1 | 7 | 1023 254 63 | 63 | 976751937 |
| 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
MBR Partition Information (HD1) Continued:
+====+====+=============+====+=============+===========+===========+
| 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
+====+====+=============+====+=============+===========+===========+
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 16128 Total Sectors: 976751937
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 63
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x03A380D40
MFT LCN: 0x02
MFT Mirr LCN: 0x030
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x8474CD5532358058
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
C:\MBR_Backup\makebt>

[wimb]

Sorry, no txt or logs but here's cmd results:
C:\>echo %DATE%
Sat 05/02/2009

Thanks for the Info.
The output of PARTINFW.EXE is OK.

The problem is in the forward slash in the DATE which is not accepted in file or foldernames.

I will improve the code.
Thanks again for finding this bug

[wimb]

=
PROGRAM UPDATE - U_XP_SET Package - Install XP from USB

Fixed - Indicated Copy Time in Make_USB.exe was too small and wrong by factor 2.5
Fixed - MBR_Backup.cmd could not run when DATE contained forward slash instead of - sign

Thanks to amalux for reporting problem when running MBR_Backup.cmd

[amalux]

=
PROGRAM UPDATE - U_XP_SET Package - Install XP from USB

Fixed - Indicated Copy Time in Make_USB.exe was too small and wrong by factor 2.5
Fixed - MBR_Backup.cmd could not run when DATE contained forward slash instead of - sign

Thanks to amalux for reporting problem when running MBR_Backup.cmd

Works!

[wimb]

maanu
The Format Stick option of Make_USB.exe is limited to Removable Devices and cannot be used for USB-sticks seen as Fixed due to e.g. install of a filter driver.
Fixed disks you can format easily with Windows XP Disk Management.

[Lancelot]

Hi wimb

I guess now i can break some concentration
It is wonderful to get so many experience with mini clicks, Thanks a lot for gathering all in one.
For now Just 2 minor requests

1) dmadmin.exe is also available on XPx64 and 2k3x64, which also can be used for processes (i always use )
but current app cant find dmadmin.exe so cant copy

to find & copy dmadmin.exe on hostosx64, you need to break "Windows x64 lines for x86 apps" and than put the lines back in,
with au3 coding you need to use this line before and after find&copy
If @ProcessorArch = "X64" Then DllCall("kernel32.dll", "int", "Wow64DisableWow64FsRedirection", "int", 1)
I dont know au3 coding, code taken from a friend but i test and working,
same is available with our lovely batcher too, look the end of post242 for an example.

This little feature have a looong story me kung with peter , remembering old days

2) Pstart dont close at once , i realised when i open close lots of times, lots of pstart at taskmanager . I guess many user may do like me, if you think like that: settings->when closed->exit application ( see picture ) , if not no problem

[wimb]

with au3 coding you need to use this line before and after find&copy
If @ProcessorArch = "X64" Then DllCall("kernel32.dll", "int", "Wow64DisableWow64FsRedirection", "int", 1)

Thanks Lancelot, I will certainly add this line to the program
so that damadmin.exe can also be found on x64 Windows.

2) Pstart dont close at once , i realised when i open close lots of times, lots of pstart at taskmanager :

Do you launch PStart then from different locations, since normally repeatedly launching PStart will give only one tray icon.

[Lancelot]

also be found on x64 Windows.

xp64, 2k364

Do you launch PStart then from different locations, since normally repeatedly launching PStart will give only one tray icon.

uppps, true. But still it annoys , after clicking X i need to exit from task. (well i copy from one place to another a lot ). Anyway no problem to me, i use pstart for some tasks too and do this setting. Very get used to make this setting again when i get from others, no problem to me just noticed

[wimb]

=
PROGRAM UPDATE - U_XP_SET Package - Install XP from USB

In Make_USB.exe program:

• Added : Install of Grub4dos MBR BootCode Selectable, which allows to make Bootable USB-sticks without the need of having XP Setup Source.
  In this case Grub4dos grldr BootLoader can e.g. direct Boot CD ISO or DOS floppy images or chainload BOOTMGR of Vista or Windows 7 Setup Source.
• Changed : Value of Calculated CopyTime as displayed in statusbar.
• Changed : Size of Dummy Second Partition in Format Stick procedure was reduced to 1 Cylinder corresponding to 8 MB
• Changed : Disconnect not needed anymore for FAT32 and FAT in Format Stick procedure by making use of touchdrv.exe

General Changes:

• Changed : Reduced the need of selecting Windows XP Setup source folder by making use of XP Bootfiles in makebt\Boot_XP folder.
• Changed : Grub4dos Updated to version grub4dos-0.4.4-2009-05-13
• Changed : Graphical User Interface improved to allow display of long filepath.

=

=

[Lancelot]

Hi wimb

here is a bugy when i first start Make_USB.exe , old version of Make_USB.exe didnt give such an error
http://img22.imagesh...2/3948/wimb.png
maybe a x64 related buggy
rest--> thanks for xp/2k3-x64 dmadmin support, just tested with my ufd and everything works nicely


guessing this bugy is a minor issue here is my last demand - vdk.exe x64 support:
well i dont know where vdk.exe used in your package but i dont see x64 of vdk.exe which will be a problem when used!
issue1 solution1:
At post 6 i solved the problem with using sfx packages for vdk, check the post you will understand .
issue2 solution2:
in the past it is found out that vdk.exe (x64) dont like vista64sp1 much, long story to short: i solved the problem with using unique folder names by using yearmonthdatehourminutesecond (20090515011321)
simply
with first using of vdk.exe i create a unique temp folder with current date 20090515011321 and copy vdk.exe & .sys here and use it from there, in the end i unmount disconnect...etc vdk
when i use vdk.exe 2nd time again i create a unique temp folder with current date 20090515011342 and copy vdk.exe & .sys here and use it from there.........
==>so far this fix is only for vistax64sp1, but it is used for all hostosx64 hostos in LiveXP project (no report since than ).


Thanks for hard work

[wimb]

Thanks Lancelot for testing Make_USB.exe

It seems by giving x64 support to find dmadmin.exe by using the "Wow64DisableWow64FsRedirection" statement,
that we have lost the ability to find MSIMG32.dll

If this is the case, then I have to remove that statement, since it is more serious then not finding dmadmin in Windows XP x64 version.
May be you can do some more testing and determine if the problem persists.
On first use of Make_USB.exe the program will copy dmadmin.exe to the makebt folder, where it can also be found easily without the Wow64 statement.

vdk.exe is not used by the GUI exe programs, so that is not giving the MSIMG32.dll missing file bug.
It was used only by the old BOOT_IMG.cmd batch program and by Mount_IMG.cmd
Of course vdk.exe for x64 support can be added to the makebt folder of U_XP_SET package.

May be the best is to remove the Wow64 statement and let x64 users copy dmadmin.exe to the makebt folder either manually or by running the program once on 32 bits XP.

[Lancelot]

wimb

give me some time to find right codes, i can write with .script but cant with .au3, need to ask blue_life support

[Lancelot]

@all: this post is about minor x64 compatilibity issue


@wimb

Hi wimb

we made various tests with blue life, better to share our findings with comunity for further x64 support.

after loooong icq and tests with blue_life , here is a quick fix, moving 1 line and replacing:

If @ProcessorArch = "X64" Then DllCall("kernel32.dll", "int", "Wow64DisableWow64FsRedirection", "int", 1)
If FileExists(@ScriptDir & "\makebt\bs_temp") Then DirRemove(@ScriptDir & "\makebt\bs_temp", 1)
If Not FileExists(@ScriptDir & "\makebt\bs_temp") Then DirCreate(@ScriptDir & "\makebt\bs_temp")
If Not FileExists(@ScriptDir & "\makebt\dmadmin.exe") Then
If FileExists(@SystemDir & "\dmadmin.exe") Then
FileCopy(@SystemDir & "\dmadmin.exe", @ScriptDir & "\makebt\", 1)
EndIf
EndIf

to

If FileExists(@ScriptDir & "\makebt\bs_temp") Then DirRemove(@ScriptDir & "\makebt\bs_temp", 1)
If Not FileExists(@ScriptDir & "\makebt\bs_temp") Then DirCreate(@ScriptDir & "\makebt\bs_temp")
If @ProcessorArch = "X64" Then DllCall("kernel32.dll", "int", "Wow64DisableWow64FsRedirection", "int", 1)
If Not FileExists(@ScriptDir & "\makebt\dmadmin.exe") Then
If FileExists(@WindowsDir & "\System32\dmadmin.exe") Then
FileCopy(@WindowsDir & "\System32\dmadmin.exe", @ScriptDir & "\makebt\", 1)
EndIf
EndIf

fix is short, but explanation is a bit long,
simply:
deleting .\makebt\bs_temp folder manually before starting latest Make_USB.exe cause no error .

First of all au3 versions of wimb and blue_life are not the same, some findings may differ (blue_life verify he uses newer/latest version).
@OSArch is better to use than @ProcessorArch , blue_life says @ProcessorArch is not used with new au3 anymore (or not preferred, he is away now...)
we find out 2 things with au3 coding
1st) dirremove or dircreate have an effect on fileredirect
2nd) using systemroot have a bad effect on fileredirect, example this

If @OSArch = "X64" Then DllCall("kernel32.dll", "int", "Wow64DisableWow64FsRedirection", "int", 1)

MsgBox(64,"",@SystemDir)

gives syswow64 folder (not system32)

I had reports about these kind of things with winbuilder 2548 times, lets call them "Billy the Door Miracles"
To solve all (and not reporting anymore) I personally use cmd.exe for some operations when i need to support both x64 x86
simply i redirect to 1 and use cmd /c (without specifying cmd path) --> so far works good because a rule never changes for both osarc compatibility: x86 application running x64 application --> x64 application is free as a bird .

[wimb]

Thanks a lot Lancelot and blue_life
for finding a solution to the x64 problem with Make_USB.exe.

I will make a new version with most recent AutoIt3 and using @OSArch and the changes that you have have found to be working.

Interesting that syswow64 folder instead of system32 folder occurs in @SystemDir for x64 Windows XP.

[wimb]

@Lancelot

A new test version U_XP_x64.exe was made.

EDIT: U_XP_SET.exe Ready for use now.

Will you please test if all x64 issues are gone.
If OK, then I can Update the U_XP_SET.exe package.

[Lancelot]

@wimb

the one you sent couldnt copy dmadmin.exe on hostosx64 ........
only adding 2 lines fix the last make_usb.exe
But
because we are good guys (me and blue_life) we work harder to get your life easier for further hostosx64 support.
We add a function which resembles same with winbuilder scripting,
reminding: with winbuilder script we use:

System,FILEREDIRECT,OFF

System,FILEREDIRECT,ON

adding something like this to au3 coding have advantage so whenever you require to add x64 support for reported systemfile cases, you can add 2 lines easly and freely to your code (on,off )
(well for now i find time only test usb boot part of your great package)
What we done is a bit different from wb script or usual au3 coding to make your life easier, so you can focus on other things than hostosx64 support.
SystemFileRedirect("On") turn fileredirect On
SystemFileRedirect("OFF") turn fileredirect back to its previous state

Here are added function and fix to existant code

Func SystemFileRedirect($Wow64Number)
If @OSArch = "X64" Then
Local $WOW64_CHECK = DllCall("kernel32.dll", "int", "Wow64DisableWow64FsRedirection", "ptr*", 0)
If Not @error Then
If $Wow64Number = "On" And $WOW64_CHECK[1] <> 1 Then
DllCall("kernel32.dll", "int", "Wow64DisableWow64FsRedirection", "int", 1)
ElseIf $Wow64Number = "Off" And $WOW64_CHECK[1] <> 0 Then
DllCall("kernel32.dll", "int", "Wow64EnableWow64FsRedirection", "int", 1)
EndIf
EndIf
EndIf
EndFunc

If FileExists(@ScriptDir & "\makebt\bs_temp") Then DirRemove(@ScriptDir & "\makebt\bs_temp", 1)
If Not FileExists(@ScriptDir & "\makebt\bs_temp") Then DirCreate(@ScriptDir & "\makebt\bs_temp")
SystemFileRedirect("On")
If Not FileExists(@ScriptDir & "\makebt\dmadmin.exe") Then
If FileExists(@WindowsDir & "\system32\dmadmin.exe") Then
FileCopy(@WindowsDir & "\system32\dmadmin.exe", @ScriptDir & "\makebt\", 1)
EndIf
EndIf
SystemFileRedirect("Off")

here is a working make_usb.exe on hostosx64 using SystemFileRedirect("XXXX")
http://lancelot.winb...00905161426.rar

I hope you like


But if you dont, the 2 line quick fix is this:

If FileExists(@ScriptDir & "\makebt\bs_temp") Then DirRemove(@ScriptDir & "\makebt\bs_temp", 1)
If Not FileExists(@ScriptDir & "\makebt\bs_temp") Then DirCreate(@ScriptDir & "\makebt\bs_temp")
If @OSArch = "X64" Then DllCall("kernel32.dll", "int", "Wow64DisableWow64FsRedirection", "int", 1)
If Not FileExists(@ScriptDir & "\makebt\dmadmin.exe") Then
If FileExists(@WindowsDir & "\system32\dmadmin.exe") Then
FileCopy(@WindowsDir & "\system32\dmadmin.exe", @ScriptDir & "\makebt\", 1)
EndIf
EndIf
If @OSArch = "X64" Then DllCall("kernel32.dll", "int", "Wow64EnableWow64FsRedirection", "int", 1)

ps: thanks for adding vdk x64 support

[wimb]

@Lancelot and @blue_life

Thanks for making Function SystemFileRedirect for solving x64 issue.

Unfortunately I don't have x64 Windows version to test the Make_USB.exe that you have made in which Function SystemFileRedirect is used.

I will make a new test version U_XP_x64.exe package and let you know when it is ready for download.

Thanks and Cheers,

[Lancelot]

Unfortunately I don't have x64 Windows...

Always ready to test & support for wonderful utilities like yours .
Once you get used to, it is really very easy to add x64 support

To get more examples, search

System,FILEREDIRECT,OFF

in livexp scripts, you will notice

System,FILEREDIRECT,ON

always follows after . you will see in which rare (but important) cases (and very low in number) we use this feature.

highly probably:

System,FILEREDIRECT,OFF

=

If @OSArch = "X64" Then DllCall("kernel32.dll", "int", "Wow64DisableWow64FsRedirection", "int", 1)

System,FILEREDIRECT,ON

=

If @OSArch = "X64" Then DllCall("kernel32.dll", "int", "Wow64EnableWow64FsRedirection", "int", 1)

different systemfileredirect function we offer maybe good for loooong codes you write, maybe not... you decide. Just dont see hostosx64 support complicated. You have testers (lancelot, blue_life), au3 coder with x64 experience (blue_life), wb scripts using this, super advanced x64 professionals (fxscrpt), and our guru peter psc who like to say "wb suppports hostosx64 successfully" in all cases .

Imagine me without being a coder (without blue_life and fxscprt) trying to explain peter psc my issues with hostosx64 (that times wb was not supporting x64), you are definately very lucky

Cu