Jump to content

Clover General discussion


ErmaC
29,818 posts in this topic

Recommended Posts

Guest ricoc90

Hi,

I'm having the same issue as artur_pt

Undefined symbols for architecture x86_64:
  "_gEfiHashAlgorithmSha1Guid", referenced from:
      _HSGetHashSize in HashServiceFix.lib(HashServiceFix.obj)
      _HSHash in HashServiceFix.lib(HashServiceFix.obj)
      _HSTestExistingShaImpl in HashServiceFix.lib(HashServiceFix.obj)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [/Users/rico/src/edk2/Build/Clover/RELEASE_XCODE9/X64/Clover/Protocols/HashServiceFix/HashServiceFix/DEBUG/HashServiceFix.dll] Error 1

build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/rico/src/edk2/Build/Clover/RELEASE_XCODE9/X64/Clover/Protocols/HashServiceFix/HashServiceFix]


build.py...
 : error F002: Failed to build module
	/Users/rico/src/edk2/Clover/Protocols/HashServiceFix/HashServiceFix.inf [X64, XCODE9, RELEASE]

- Failed -
Build end time: 23:06:20, Apr.11 2018
Build total time: 00:00:08

 

3 hours ago, Funky frank said:

Or any idea how I could remove the 1st hfs+ partition and then resize the second to the full space?

Clone your second partition to your first partition (e.g. by using CCC), then remove the second partition and expand the first partition using Disk utility

Link to comment
Share on other sites

5 hours ago, artur_pt said:

hello Zenith432

rev 4433 is broken

  Reveal hidden contents

Undefined symbols for architecture x86_64:

  "_gEfiHashAlgorithmSha1Guid", referenced from:

      _HSGetHashSize in HashServiceFix.lib(HashServiceFix.obj)

      _HSHash in HashServiceFix.lib(HashServiceFix.obj)

      _HSTestExistingShaImpl in HashServiceFix.lib(HashServiceFix.obj)

ld: symbol(s) not found for architecture x86_64

clang: error: linker command failed with exit code 1 (use -v to see invocation)

make: *** [/Users/artur_pt/src/edk2/Build/Clover/RELEASE_XCODE5/X64/Clover/Protocols/HashServiceFix/HashServiceFix/DEBUG/HashServiceFix.dll] Error 1

 

 

build.py...

: error 7000: Failed to execute command

make tbuild [/Users/artur_pt/src/edk2/Build/Clover/RELEASE_XCODE5/X64/Clover/Protocols/HashServiceFix/HashServiceFix]

 

 

build.py...

: error F002: Failed to build module

/Users/artur_pt/src/edk2/Clover/Protocols/HashServiceFix/HashServiceFix.inf [X64, XCODE5, RELEASE]

 

- Failed -

Build end time: 18:50:57, Apr.11 2018

Build total time: 00:01:23

thanks

@zenith432  posted a fix like this: 

gEfiHashAlgorithmSha1Guid is multiply-defined in MdePkg/MdePkg.dec

#if 0
EFI_GUID gEfiHashAlgorithmSha1Guid = EFI_HASH_ALGORITHM_SHA1_GUID;
#endif

instead of perhaps something more like this?

#ifndef gEfiHashAlgorithmSha1Guid
EFI_GUID gEfiHashAlgorithmSha1Guid = EFI_HASH_ALGORITHM_SHA1_GUID;
#endif

 

Edited by tluck
  • Like 1
  • Thanks 1
Link to comment
Share on other sites

I accepted the workaround while I didn't understand why the guid is not defined and why it is not found in MdePkg.dec. Looks like a mistake in EDK2 build system.

Link to comment
Share on other sites

3 hours ago, Slice said:

I accepted the workaround while I didn't understand why the guid is not defined and why it is not found in MdePkg.dec. Looks like a mistake in EDK2 build system.

This workaround is useless because gEfiHashAlgorithmSha1Guid is a global variable, not a preprocessor symbol so "#ifndef gEfiHashAlgorithmSha1Guid" is always true.

When compiling with GCC on both macOS and Linux I get multiply defined symbol error because of definition in MdePkg.dec (which ends up in AutoGen.c for HashServiceFix module) and HashServiceFix.c.

arthurpt and ricoc90 report above is about Xcode build.

So I suggest replacing  "#ifndef gEfiHashAlgorithmSha1Guid" with "#if !defined(__GNUC__) || defined(__clang__)", so that gEfiHashAlgorithmSha1Guid is defined in HashServiceFix.c if not compiling on GCC.  Let me know if it's ok, I'll commit it.

Edited by Zenith432
Link to comment
Share on other sites

16 hours ago, Funky frank said:

I have a macos drive with macos on the 2nd hfs+ partition. Is there any way to show up this partition as bootdrive in the clover menu

Or any idea how I could remove the 1st hfs+ partition and then resize the second to the full space?

 

Hi again,

I was now able to relocate the 2nd partition to the starting point of partition 1, using the paragon harddrive manager demo.

Still I am sadly unable to see this drive in the clover boot drives list. The drive is named "OSX". Here is the partition table:
 

/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *320.1 GB   disk0
   1:               Windows_NTFS Win8Boot                367.0 MB   disk0s1
   2:               Windows_NTFS Win8System              319.2 GB   disk0s2
   3:                       0x27                         471.7 MB   disk0s3

/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.8 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                  Apple_HFS OSX                     1.7 TB     disk1s2

/dev/disk2 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS OSXSSD                  499.8 GB   disk2s2

/dev/disk3 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *4.0 TB     disk3
   1:                        EFI EFI                     209.7 MB   disk3s1
   2:                  Apple_HFS OSX2                    4.0 TB     disk3s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk3s3

 

I only see "OSXSSD" and "OSX2". What could be the cause for this?

Thanks for ideas!

P.S.: "OSX" contains a 1:1 copy of "OSXSSD" and is HFS+ formatted, just like "OSXSSD".

P.S.2: Was I meant to use a hybrid partition table instead purely GPT? Also can I still set an active partition on a pure GPT?

Edited by Funky frank
Link to comment
Share on other sites

1 hour ago, Zenith432 said:

This workaround is useless because gEfiHashAlgorithmSha1Guid is a global variable, not a preprocessor symbol so "#ifndef gEfiHashAlgorithmSha1Guid" is always true.

When compiling with GCC on both macOS and Linux I get multiply defined symbol error because of definition in MdePkg.dec (which ends up in AutoGen.c for HashServiceFix module) and HashServiceFix.c.

arthurpt and ricoc90 report above is about Xcode build.

So I suggest replacing  "#ifndef gEfiHashAlgorithmSha1Guid" with "#if !defined(__GNUC__) || defined(__clang__)", so that gEfiHashAlgorithmSha1Guid is defined in HashServiceFix.c if not compiling on GCC.  Let me know if it's ok, I'll commit it.

Why not just remove the definition from the HashServiceFix.c, uncomment from in HashServiceFix.inf, and add the definition to CloverPkg.dec? I should have fixed it for r4436.

 

36 minutes ago, Funky frank said:

 

Hi again,

I was now able to relocate the 2nd partition to the starting point of partition 1, using the paragon harddrive manager demo.

Still I am sadly unable to see this drive in the clover boot drives list. The drive is named "OSX". Here is the partition table:
 


/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *320.1 GB   disk0
   1:               Windows_NTFS Win8Boot                367.0 MB   disk0s1
   2:               Windows_NTFS Win8System              319.2 GB   disk0s2
   3:                       0x27                         471.7 MB   disk0s3

/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.8 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                  Apple_HFS OSX                     1.7 TB     disk1s2

/dev/disk2 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS OSXSSD                  499.8 GB   disk2s2

/dev/disk3 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *4.0 TB     disk3
   1:                        EFI EFI                     209.7 MB   disk3s1
   2:                  Apple_HFS OSX2                    4.0 TB     disk3s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk3s3

 

I only see "OSXSSD" and "OSX2". What could be the cause for this?

Thanks for ideas!

P.S.: "OSX" contains a 1:1 copy of "OSXSSD" and is HFS+ formatted, just like "OSXSSD".

P.S.2: Was I meant to use a hybrid partition table instead purely GPT? Also can I still set an active partition on a pure GPT?

Do you have some sort of hiding going on? Inspect your boot.log to see what is happening with the disk scan. Or try pressing F3 to toggle hiding/showing hidden entries.

EDIT: It depends on if you are booting legacy or UEFI, if UEFI then you want pure GPT.

Edited by apianti
  • Like 1
Link to comment
Share on other sites

@apianti: Thanks for that hint. I now tried F3 in clover, but "OSX" still does not appear :(  Is it possible that the drive misses some intentional spacing between the partitions? Also the hard drive has a 20GB space at the very end, which is not allocated...

This is so weird. I really have no any further idea to what I should look at...

Under "hide" only "windows" and "win8system" will be hidden btw. I also had again a look into paragon, the size of the EFI partition seems to be exactly like on "OSXSSD"...

Edited by Funky frank
Link to comment
Share on other sites

An identical 1:1 copy to a USB drive just lists fine in clover... Is it possible that clover does not detect all available SATA ports?

edit: no, tried another data port, that is not the problem. maybe the left space after the partition is the problem?

Edited by Funky frank
Link to comment
Share on other sites

37 minutes ago, Funky frank said:

An identical 1:1 copy to a USB drive just lists fine in clover... Is it possible that clover does not detect all available SATA ports?

edit: no, tried another data port, that is not the problem. maybe the left space after the partition is the problem?

Does the drive have a hybrid MBR? It maybe sounds like a partition map issue.

  • Like 1
Link to comment
Share on other sites

12 minutes ago, apianti said:

Does the drive have a hybrid MBR? It maybe sounds like a partition map issue.

I seemed to be y hybrid gpt/mbr, but I converted it to GPT only, using paragon.

This is the GPT info, disk1 is the non listed drive, disk3 is the working ssd:

sudo gpt -r show /dev/disk1
       start        size  index  contents
           0           1         PMBR
           1           1         Pri GPT header
           2          32         Pri GPT table
          34      409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
      409634        4062         
      413696  3377972280      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
  3378385976    40267159         
  3418653135          32         Sec GPT table
  3418653167           1         Sec GPT header
sudo gpt -r show /dev/disk3
      start       size  index  contents
          0          1         PMBR
          1          1         Pri GPT header
          2         32         Pri GPT table
         34          6         
         40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
     409640  976101344      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
  976510984     262151         
  976773135         32         Sec GPT table
  976773167          1         Sec GPT header

 

It seems that there is a empty space between the two partition GPT parts...

 

Link to comment
Share on other sites

On 07/04/2018 at 3:43 AM, Pavo said:

Yeah it works without XCPM, its possible that its because I have 2x CPUs like you said. Oh well getting around 42k GB score right now anyways.

-xcpm_ipi boot flag for dual cpu im sure .. thats what i have anyway and what ssdtPrgen tells you need. 

Link to comment
Share on other sites

8 minutes ago, Download-Fritz said:

It already is in MdePkg.dec.

Yes but not in the way needed. It is under the Guids section in MdePkg.dec. It is used under the Protocols section in the module so it needs to be defined in the Protocols section in a .dec, so I added it to CloverPkg.dec.

10 minutes ago, Funky frank said:

I seemed to be y hybrid gpt/mbr, but I converted it to GPT only, using paragon.

This is the GPT info, disk1 is the non listed drive, disk3 is the working ssd:


sudo gpt -r show /dev/disk1
       start        size  index  contents
           0           1         PMBR
           1           1         Pri GPT header
           2          32         Pri GPT table
          34      409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
      409634        4062         
      413696  3377972280      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
  3378385976    40267159         
  3418653135          32         Sec GPT table
  3418653167           1         Sec GPT header
sudo gpt -r show /dev/disk3
      start       size  index  contents
          0          1         PMBR
          1          1         Pri GPT header
          2         32         Pri GPT table
         34          6         
         40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
     409640  976101344      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
  976510984     262151         
  976773135         32         Sec GPT table
  976773167          1         Sec GPT header

 

It seems that there is a empty space between the two partition GPT parts...

 

I doubt that matters. As long as it's GPT, I don't see why it wouldn't be detecting it unless something else is wrong with it. Have you tried repairing/first aid the partition?

  • Like 2
Link to comment
Share on other sites

18 minutes ago, apianti said:

I doubt that matters. As long as it's GPT, I don't see why it wouldn't be detecting it unless something else is wrong with it. Have you tried repairing/first aid the partition?

I now deleted the EFI partition and created a new EFI partition, this time slightly bigger than 209,72MB, so filling the empty space between the partitions:

sudo gpt -r show /dev/disk0
Password:
       start        size  index  contents
           0           1         PMBR
           1           1         Pri GPT header
           2          32         Pri GPT table
          34        2014         
        2048      411648      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
      413696  3377972280      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
  3378385976    40267159         
  3418653135          32         Sec GPT table
  3418653167           1         Sec GPT header

 

Now clover seems to detect this EFI partition as Windows EFI boot... I guess clover detects macos EFI simply by exact size?

So I would assume that clover

- is not capable of detecting empty space between EFI- and system-partition

- will detect macos efi system partition only by exact EFI partition size?

 

Link to comment
Share on other sites

15 minutes ago, Funky frank said:

I now deleted the EFI partition and created a new EFI partition, this time slightly bigger than 209,72MB, so filling the empty space between the partitions:


sudo gpt -r show /dev/disk0
Password:
       start        size  index  contents
           0           1         PMBR
           1           1         Pri GPT header
           2          32         Pri GPT table
          34        2014         
        2048      411648      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
      413696  3377972280      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
  3378385976    40267159         
  3418653135          32         Sec GPT table
  3418653167           1         Sec GPT header

 

Now clover seems to detect this EFI partition as Windows EFI boot... I guess clover detects macos EFI simply by exact size?

So I would assume that clover

- is not capable of detecting empty space between EFI- and system-partition

- will detect macos efi system partition only by exact EFI partition size?

 

Clover detects macOS from the HFS+ partition as that is where the OS loader is. There must be something wrong with the partition map or the parition/volume itself.

  • Like 1
Link to comment
Share on other sites

@apianti: your solution in Rev 4436 does not work with GCC.  Since gEfiHashAlgorithmSha1Guid is defined both in CloverPkg.dec and MdePkg.dec, its C definition is inserted into AutoGen.c for HashServiceFix twice which cause compilation to break.

I have not checked with Xcode.

Link to comment
Share on other sites

33 minutes ago, apianti said:

Yes but not in the way needed. It is under the Guids section in MdePkg.dec. It is used under the Protocols section in the module so it needs to be defined in the Protocols section in a .dec, so I added it to CloverPkg.dec.

Big thanks for the explanation!

I encountered this message

Quote

build.py...
/Users/sergey/src/edk2/Clover/Protocols/HashServiceFix/HashServiceFix.inf(31): error 4000: Value of Protocol [gEfiHashAlgorithmSha1Guid] is not found under [Protocols] section in
    /Users/sergey/src/edk2/Clover/CloverPkg.dec
    /Users/sergey/src/edk2/MdePkg/MdePkg.dec
    /Users/sergey/src/edk2/MdeModulePkg/MdeModulePkg.dec
    /Users/sergey/src/edk2/IntelFrameworkPkg/IntelFrameworkPkg.dec
 

- Failed -
 

but I miss words about section.

EDK2 is right. The GUID is defined correctly. It is not protocol and must be defined under [Guids] section as MdePkd did.

Sorry I will remake this solution again. Rev 4437

  • Like 1
Link to comment
Share on other sites

4 hours ago, apianti said:

Clover detects macOS from the HFS+ partition as that is where the OS loader is. There must be something wrong with the partition map or the parition/volume itself.

Hm, ok thanks for this info. What is clover exactly looking for on the HFS+ partition? Only /Sys/Lib/Kernels/kernel ?  What files do have to exist to make it appear in the list?

 

btw. these are the bootlog entries:

3:569  0:001  === [ ScanLoader ] ========================================
3:569  0:000  - [05]: 'Win8Boot'
3:569  0:000  - [06]: 'Win8System', hidden
3:569  0:000  - [07]: 'ntfsrest', hidden
3:569  0:000  - [08]: 'EFI'
3:570  0:000  - [09]: 'OSX2'
3:649  0:079          AddLoaderEntry for Volume Name=OSX2
3:719  0:070      hibernated: set as never
3:778  0:058  - [10]: 'Recovery HD'
3:778  0:000          AddLoaderEntry for Volume Name=Recovery HD
3:809  0:031  - [11]: 'EFI'
3:812  0:002  - [13]: 'EFI'
3:815  0:003  - [14]: 'OSXSSD'
3:819  0:004          AddLoaderEntry for Volume Name=OSXSSD
3:822  0:002      hibernated: set as never
3:824  0:002  Scanning legacy ...
3:824  0:000   5: 'Win8Boot' (vista,win) add legacy
3:825  0:000   added 'Boot Windows from Win8Boot' OSType=2 Icon=vista,win
3:825  0:000   6: 'Win8System' (vista,win) hidden
3:825  0:000   7: 'ntfsrest' (vista,win) hidden
3:825  0:000  11: 'EFI' (win) add legacy
3:825  0:000   added 'Boot Windows from EFI' OSType=2 Icon=win

That new "EFI" entry really seems to come from the EFI partition of "OSX" and will be falsely listed as windows...?

Edited by Funky frank
Link to comment
Share on other sites

8 minutes ago, Slice said:

Clover looks for file boot.efi to mark the HFS+ partition to be loadable.

Thanks for info.

But on the "OSX" HFS+ partition, there is a 571.960 bytes sized "boot.efi" under /System/Library/CoreServices/boot.efi.

Also more log:

3:825  0:000  === [ AddCustomTool ] =====================================
3:830  0:005  found tool \EFI\CLOVER\tools\Shell64U.efi
3:830  0:000  Checking EFI partition Volume 8 for Clover
3:831  0:001  Checking EFI partition Volume 11 for Clover
3:845  0:014   Found Clover
3:846  0:000  === [ GetEfiBootDeviceFromNvram ] =========================
3:846  0:000   - found entry 2. 'Boot macOS from OSXSSD', Volume 'OSXSSD', DevicePath 'PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0xFFFF,0x0)\HD(2,GPT,8718D221-ECD2-4374-XXXX-AAB2D2CEA036,0x64028,0x3A2E1FE0)\System\Library\CoreServices\boot.efii'
3:846  0:000  DefaultIndex=2 and MainMenu.EntryCount=11
3:875  0:028  GUI ready
5:876  2:001  === [ StartLoader ] =======================================

So it cannot find the boot.efi on "OSX", even if I see here that it is there...

Btw. notice the typo? in the log "boot.efii' instead "boot.efi"...

Also why is it getting the info only from nvram? "GetEfiBootDeviceFromNvram"...

Edited by Funky frank
Link to comment
Share on other sites

1 hour ago, Funky frank said:

Also why is it getting the info only from nvram? "GetEfiBootDeviceFromNvram"...

can you temporarily remove EmuVariable and then reboot?

looks like you played with boot camp assistant (why you had an hybrid MBR):

// UEFI boot: get gEfiBootDeviceGuid from NVRAM.
    // if present, ScanVolumes () will skip scanning other volumes in the first run.
    // this speeds up loading of default OSX volume.
    GetEfiBootDeviceFromNvram ();

it's in your nvram.plist

Edited by vector sigma
  • Like 1
Link to comment
Share on other sites

Hi, I am not using emuvariable, but real nvram from the board. I already cleaned the nvram (there were lots of efi-apple-payload entries, but no change).

So could I select the other drive in the macos settings as boot device and it would work? I am afraid of setting this, so the computer would not boot at all anymore...

Link to comment
Share on other sites

12 minutes ago, Funky frank said:

Hi, I am not using emuvariable, but real nvram from the board. I already cleaned the nvram (there were lots of efi-apple-payload entries, but no change).

So could I select the other drive in the macos settings as boot device and it would work? I am afraid of setting this, so the computer would not boot at all anymore...

Looks like is still in your nvram, otherwise how can be printed in your log?. Unless Clover adds this using something like a default volume taken from the config plist... 

Can you show me a screenshot of your nvram using Clover Configurator Pro or nvram -p?

Edited by vector sigma
Link to comment
Share on other sites

8 minutes ago, vector sigma said:

Looks like is still in your nvram, otherwise how can be printed in your log?. Unless Clover adds this using something like a default volume taken from the config plist... 

Can you show me a screenshot of your nvram using Clover Configurator Pro or nvram -p?

Sure. This is after a nvram clearing and a reboot of Sierra:

nvram -p
fakesmc-key-MSWr-ui8	%00
fakesmc-key-RPlt-ch8*	j17%00%00%00%00%00
fakesmc-key-RBr -ch8*	j16j17%00%00
EFILoginHiDPI	%01%00%00%00
fakesmc-key-#KEY-ui32	%00%00%00%00
SystemAudioVolumeDB	%80
fakesmc-key-BATP-flag	%00
EFIBluetoothDelay	%b8%0b
fakesmc-key-MSTc-ui8	%00
fakesmc-key-BNum-ui8	%00
security-mode	none
csr-active-config	g%00%00%00
fakesmc-key-$Num-ui8	%01
fakesmc-key-MSFW-ui8	%01%00
fakesmc-key-REV -ch8*	%02%15%0f%00%00%07
fakesmc-key-MSPS-ui16	%00%03
fakesmc-key-$Adr-ui32	%00%00%03%00
fakesmc-key-EPCI-ui32	%07%a0%07%00
bluetoothActiveControllerInfo	%01%00%12%0a%01%00%00%00%12%1a%00%1a}%daq%0c
nvda_drv	1%00
fakesmc-key-MSAc-ui16	%00%00
SystemAudioVolume	%80
fakesmc-key-RMde-char	A
specialbootdevice	%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%03%00%ff%ff%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00%e0%1f.:%00%00%00%00Q%d2%18%87%d2%ectC%b4%95%aa%b2%d2%ce%a06%02%02%7f%ff%04%00
fakesmc-key-BEMB-flag	%00

 

Link to comment
Share on other sites

×
×
  • Create New...