Database Info

[KERNEL][32B]cm-kernel 2.6.29-bfs with BFS-302

I built a cm-kernel from Cyanogen's git repository for you to use. For now it is just a boot.img and wlan.ko, but I am going to make an update.zip for you as soon as I have time
Thanks to: cyanogen, rikupw, bcrook and Radix
This boot.img is only tested on CyanogenMod 4.1.11.1 and might work with older versions. But not on non-CyanogenMod roms!
I've also made some instructions for you to use if you want to build your own kernel: http://ostebaronen.dk/?p=210
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Get the two files here:
BFS-300:
http://ostebaronen.dk/android/cm-kernel-2.6.29-bfs300/boot.img
http://ostebaronen.dk/android/cm-kernel-2.6.29-bfs300/wlan.ko
BFS-302:
http://ostebaronen.dk/android/cm-kernel-2.6.29-bfs302/boot.img
http://ostebaronen.dk/android/cm-kernel-2.6.29-bfs302/wlan.ko
To put it on your phone do as follows.
Code:
adb shell mount -o rw,remount /system
adb push wlan.ko /system/lib/modules
adb push boot.img /sdcard
adb shell
cat /dev/zero > /dev/mtd/mtd2
ignore no space left error.
flash_image boot /sdcard/boot.img
ignore read all-zero errors.
DISCLAIMER: I take no responsibility of bricking your phone, remember always to do nandroid backups! I will try to answer questions you ask here, off-topic questions will be ignored.

Lemme know if you need any help making a kernel update.zip. I would be happy to help out.

Oste
Thanks again! worked 100% well for me

i thing this kernel work for 32b

Very nice information. How about a guide for the pre build?

eViL D: said:
Very nice information. How about a guide for the pre build?
Click to expand...
Click to collapse
What do you mean, for making the boot.img?

I've found out compcache doesn't work, going to look at it.

Or wait, module works fine if I load it myself. So compcache can be enabled with.
Code:
modprobe ramzswap
/system/bin/rzscontrol /dev/block/ramzswap0 --init
swapon /dev/block/ramzswap0
Strange though, because the a2sd script should do this for us...

I know why compcache isn't working for you
Kernel versions and modules are intrinsicly linked by 'uname -r'
Cyanogen's kernel uses 2.6.29-cm41 and you've changed the name with yours to be different - so it's not going to load the modules automagically.
Those modules are slightly hidden from view too - they're in modules.sqf which is a squash4 volume that is mounted on boot.
Good job on documenting the git commands to track cyanogen's builds tho - this is what I need!

cat: write error: No space left on device
????

kchau said:
cat: write error: No space left on device
????
Click to expand...
Click to collapse
i get the same thing

i skipped cat zero
and it hangs at the mytouch screen:
K:\>adb logcat
I//system/bin/sh( 51): /system/bin/sh: Can't open /system/bin/a2sd
I/logwrapper( 51): /system/bin/sh terminated by exit(2)
on dwangs 1.6 rom, never had a2sd to begin with

OK, going to rebuild it for you with the correct uname. Lets see if that solves the modules problems, after that I will look at putting it inside a update.zip. bcrook gave me some guidance so it should be fairly easy

Updated kernel recompiled with the correct uname!

kchau said:
cat: write error: No space left on device
????
Click to expand...
Click to collapse
This is because cat continues filling the device with zeroes until the device is full. So you are ought to get the error No worries. Though this command is not necessary, but good to do since you are sure that nothing is left on it.

OK, for some reason no matter what I do on my phone it will not activate compcache automatically. I tried wiping and installing stock cm4.1.11.1 it didn't work there aswell. So I am sure it is not the kernels fault.
Could someone please confirm compcache is working for them?

will i still have the same a2sd hang on the mytouch screen now?

kchau said:
will i still have the same a2sd hang on the mytouch screen now?
Click to expand...
Click to collapse
What do you mean?
UPDATE:
Ok compcache is working. It seems the a2sd script does not like it when you dont have partitioned your SDcard. If you need help setting it up, ask away!

So what is the difference between the BFS in this kernel & the BFS is cm4.1.11.1? Is this one faster?
Edit: You just stated compcache is working if the sdcard is partitioned... so if we are already partitioned, we shouldn't have any problems, correct? Or do we have to reformat?

Cheesebaron said:
What do you mean?
UPDATE:
Ok compcache is working. It seems the a2sd script does not like it when you dont have partitioned your SDcard. If you need help setting it up, ask away!
Click to expand...
Click to collapse
when im on dwangs rom, it hangs at the mytouch screen, and adb logcat has this message
K:\>adb logcat
I//system/bin/sh( 51): /system/bin/sh: Can't open /system/bin/a2sd
I/logwrapper( 51): /system/bin/sh terminated by exit(2)
i dont think dwang's rom is a rom with a2sd, and i dont have it partitioned in my sd either.
however, when im on 4.0.4, and still dont have a partitioned sdcard, everything works fine

[Tutorial] How to change kernel logo (1st boot srceen) [COMPLETED]

We have 3 major works here... So I gonna to make it seperated
-1st post is HOW TO EXTRACT kernel.img (boot.img)
-2nd post is HOW TO CONVERT PICTURE FILE to BOOT.RLE
-3rd post is HOW TO REPACK THE KERNEL PAKAGE into boot.img
Requiredment
-Window machine
-installed cygwin
-the full boot.img/kernel (some kernel won't work because there is no full pakage/ i mean we can't)
-bootimg.zip (tool for UNPACK and REPACK kernel)
-boot_screen_logo_creation_package.rar
Thank and Credit
i- Credit to DooMLoRD Recognized Developer over most of XPERIA devices for his own tool and tutor that I learned before
ii- Credit to jimbo77 Senior Member for his tutorial that I used and learned and tool for unpack and repack
ii- Don't forget to give them a thanks meter
=============================================================================
Here we go
1-This section I will show u how to unpack and repack the boot.img
just see from original thread by jimbo77 from here and download the UNPACK and REPACK tool by him HERE
this is a fast guide from me:-
1-extract the bootimg-tools.zip into new folder (name it 'boot' folder)
2-move it into cygwin directory (cygwin/boot)
3- move your fav kernel into same directory
4-run cygwin.bat
cd /boot
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5-Now, unpack your boot.img by running the following command:
./extractboot boot.img
Click to expand...
Click to collapse
If your output looks like this, then the extraction has worked correctly! Note that the Command Line string has also been read from the source file, this will be used later when you go to re-pack your file.
Your script folder should now look like this:
boot.img-kernel is the compiled kernel blob that was inside the source boot.img, if you want to replace the kernel with another compiled kernel image, you can replace this file with another one (but leave the file name the same)
boot.img-ramdisk.gz is the gzipped ramdisk image which has been split from the boot.img, you should leave this file alone.
The “out” folder contains the EXTRACTED ramdisk, and this is where you should make your changes to the ramdisk.
Important Note!
Remember, when editing files in the ramdisk through Windows, such as init.rc, Windows notepad will not format the files correctly, making them almost impossible to read, wheras Wordpad will LOOK like it is formatting the files correctly, if you save one of these files from the Wordpad application it will BREAK the file and it will no longer be able to be read correctly by Android. To edit these files you MUST use an editor such as Notepad++ which you can download for free.
AGAIN...
Special thanks/credit to jimbo77 for his excellent guide

So.. NEXT step to change a kernel logo is here
Requiredment
1-a picture what are u like to look into the 1st boot screen (kernel logo) (make sure it size/resolution same your device resolution)
2-boot_screen_logo_creation_package.rar
3-some infos and knowledges here
4-window machine like i explained on 1st post
My quick guide
-extract the tool.rar
-move extracted files into new folder (name it 'rle' folder without quote)
-move into cygwin folder (to make it easy to follow my simple guide)
-copy your own logo.png (a picture u want to use on a kernel) into same rle folder
(for 4 steps above it shold look like tis)
-now launch cygwin.bat
cd /rle
Click to expand...
Click to collapse
./convert_image_to_rle.bat logo.png
Click to expand...
Click to collapse
Ah...my mistake..don't forget to move/copy/replace new logo.rle into
C/cygwin/boot/out/ramdisk/here
if you done good...follow next step on next post (to repack your moded kernel)

Last step before you flash a new look kernel (boot.img) is
Repack your moded kernel
./packboot
Click to expand...
Click to collapse
One thing to note that people may mention in other guides, is that when packing boot.img files, you will usually have to declare a base address, and a command line to the packaging tool. This set of scripts reads the existing command line and base address from the boot.img file you originally provided at the time of repacking, so always make sure you leave your original source boot.img file in the folder and do not re-name it after extraction, your newly created boot.img file will be named boot_new.img and will NOT overwrite the original.
Done! If your screen looks like the image above, then you should now have a freshly created boot_new.img file, ready to be flashed to Android for testing, you can now go ahead and flash it through FASTBOOT one thing I'll recommend though is to first do

I need this for extra (extra thanks..)
(may U?)

[Q] ICS port how to pack custom rom? devs please help.

Hello everyone,
I'd like to pay back the community that have been helping me with my cellphone, and also helped me learn a lot on how to help myself.. so i decided to give back.. i have been customizing GB and for my own personal use, now i am trying to customize ICS port by xbsall. the only problem i have is packing the rom in a flashable zip. I searched everywhere with no success all i need is how to pack the system and data to .img file.
I'd appreciate the help and i will be posting my custom rom the forums soon.
Special thanks to xbsall, defcomg, and everyone working on making the ICS possible on the O3D.

You can try this out:
ROM Factory v1.7.1[May/12/2012]
Although P920 isn't on the "Supported Devices" list...
or this:
[KITCHEN] Android Kitchen, v0.214 [Linux / Mac / Windows]
Just be careful.

Mount .IMG As Dir Named system
Code:
mkdir system
sudo mount -t ext4 -o loop system.img system/
New System
Code:
sudo cp -ar system new_system
Create New .img
Code:
sudo ./make_ext4fs -l 700m -a system system.img new_system/system
Source

defcomg said:
Mount .IMG As Dir Named system
Code:
mkdir system
sudo mount -t ext4 -o loop system.img system/
New System
Code:
sudo cp -ar system new_system
Create New .img
Code:
sudo ./make_ext4fs -l 700m -a system system.img new_system/system
Source
Click to expand...
Click to collapse
Thanks guys, I am gonna try and report back..

BadSoul said:
Thanks guys, I am gonna try and report back..
Click to expand...
Click to collapse
I tried those methods and none of it created me a .img packed rom.
Any other suggestions? please
Thank you

BadSoul said:
I tried those methods and none of it created me a .img packed rom.
Any other suggestions? please
Thank you
Click to expand...
Click to collapse
Lets suppose you have made the changes to your system the way you like it. (add/remove apps , etc)
Now in order to make your system.img
boot into cwm/twrp
connect to pc
use the following command to make the img file
adb shell
dd if=/dev/block/mmcblk0p7 of=/emmc/system.img
wait until it ends
your system.img is ready and packed into your emmc
make sure your emmc has plenty of space to fit it
now you can make a zip file with it and use the command
package_extract_file("system.img", "/dev/block/mmcblk0p7");
in your updater script to unpack
happy cooking
_____________________________________________________
the cmd output should look like this
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # cd dev
cd dev
/dev # cd block
cd block
/dev/block # dd if=/dev/block/mmcblk0p7 of=/emmc/system.img
dd if=/dev/block/mmcblk0p7 of=/emmc/system.img
1445274+0 records in
1445274+0 records out
739980288 bytes (705.7MB) copied, 126.201996 seconds, 5.6MB/s
/dev/block #reboot

Thank you very much xbsall. That worked perfectly.
Do you know can i create data.img also? most of my customization is in the data. I'd really appreciate it.
What block is it in?
Thanks for the great work.

mmcblk0p8 is data
Sent from my LG-P920 using xda app-developers app

iodak said:
mmcblk0p8 is data
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
Awesome! thanks iodak, xbsall, defcomg and TMProduct1onZ.. I really appreciate the help.

xbsall with dsixda's kitchen would there have to be a new edify_defs created for SU760 if using your XBSA404 port? The reason I am asking is I am getting an error Status 0 when creating a ROM in the kitchen. I think this may be due to the device being ro.product.device=SU760 in build.prop but not having an edify_defs for the SU760? any help appreciated.
Status 0 might be two things: 1) You used an update-script (Amend format, which is very old) when you should be using an updater-script (Edify format), or the other way around; OR 2) Your updater-script is using the "MTD" partition type when mounting a partition rather than another type such as EMMC (and thus, you need the device defined under the kitchen's /tools/edify_defs folder).

Havent used dsixda kitchen for a long long long... long time.
So i cant help you with it.
Tell me what you wanna do to your ROM.

xbsall said:
Havent used dsixda kitchen for a long long long... long time.
So i cant help you with it.
Tell me what you wanna do to your ROM.
Click to expand...
Click to collapse
Just trying to start with a basic platform by de-odexing and zip alligning and build on it from there
dsixda's kitchen seemed like the easiest method and i've managed with some degree of success but required the update binary from other peoples ROM's which I would rather not do.

Lol just adb pull/push them..

xbsall said:
Lol just adb pull/push them..
Click to expand...
Click to collapse
lol thats fine but i'd rather have a flashable zip without having to use others update binary and modified updater script :victory:
---------- Post added at 10:16 PM ---------- Previous post was at 10:13 PM ----------
I'll keep messing around with the kitchen in the meantime :laugh:
BTW that looks tremendous is it ROM: XBSA V3b ICS ROM for Optimus3D P920 with ACiD Audio?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yes its v3b

[Dump] Tab 4 7.0

Galaxy Tab 4 7.0 (3G) system dump
~~~~~~~
Apps:
HERE
~~~~~~~
priv-app - folder:
HERE
~~~~~~~
media - folder:
HERE
~~~~~~~
Framework:
HERE
~~~~~~~
lib - folder:
HERE
~~~~~~~
bin - folder:
HERE
~~~~~~~
vendor - folder:
HERE
~~~~~~~
etc - folder:
HERE
~~~~~~~
recovery.img:
(I´m not sure if this image is working please give feedback)
HERE
~~~~~~~
boot.img:
(I´m not sure if this image is working please give feedback)
HERE
~~~~~~~
build.prop:
HERE
~~~~~~~
Note: I´m not responsible for any damage to your device
~~~~~~~
Wrong device ?
Galaxy Tab 4 10.1 dump here
Galaxy Tab 4 8.0 dump Coming soon
Make your own dumps Coming soon
​

Thank you so much bro
Waiting for this \m/
Sent from an expensive Toaster (SM-T211)

Boot
Hey I'm trying to make a boot.img dump myself. Did you find out if you dumped the right mount point? I downloaded Partition Table from the play store and it shows all the mount points but I'm not sure which one is the boot. It doesn't actually specify a boot partition and if i go into the /dev/block/platform/soc,2/by-name folder it doesn't have a boot file in there or an aboot file. So I'm confused.

ubuntu is the solution
TheOriginalist said:
Hey I'm trying to make a boot.img dump myself. Did you find out if you dumped the right mount point? I downloaded Partition Table from the play store and it shows all the mount points but I'm not sure which one is the boot. It doesn't actually specify a boot partition and if i go into the /dev/block/platform/soc,2/by-name folder it doesn't have a boot file in there or an aboot file. So I'm confused.
Click to expand...
Click to collapse
Hey,
I can't help you with that using a phone.
I have done this multiple times using Ubuntu.
PHP:
sudo apt-get install abootimg
sudo abootimg -x boot.img
mkdir workspace
cd workspace
gzip -cd initrd.img | cpio -i
I could upload the dump, too !?

UAdeveloper said:
Hey,
I can't help you with that using a phone.
I have done this multiple times using Ubuntu.
PHP:
sudo apt-get install abootimg
sudo abootimg -x boot.img
mkdir workspace
cd workspace
gzip -cd initrd.img | cpio -i
I could upload the dump, too !?
Click to expand...
Click to collapse
Wait I don't quite understand did you successfully dump the boot img from the tablet? Cause it looks like your just making a boot img there (not too linux friendly I mainly use windows)

TheOriginalist said:
did you successfully dump the boot img from the tablet?
Click to expand...
Click to collapse
Yes (using the linux method) ...
Do you need it? I could upload it tomorrow

Hi, all I really need is the keyboard files but, I cannot see the files. I can ony see so many and the list cuts off. Also, I cannot download the .zips. Is there any way you could just link me to the keyboard files, please?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

UAdeveloper said:
Wrong device ?
Galaxy Tab 4 10.1 dump here
Galaxy Tab 4 8.0 dump Coming soon
Make your own dumps Coming soon
​
Click to expand...
Click to collapse
still waiting for 'make your own dumbs'

bubenking said:
still waiting for 'make your own dumbs'
Click to expand...
Click to collapse
I don`t work with Samsung Tab´s anymore, sorry.
If someone wants me to link him to his work, pm me.

GT-i8260 Pit-file

Hi all,
In Odin i checked 'Nand Erase all', resulting in losing all partition table information.
I have tried to extract a PIT-file from another GT-i8260 using this adb command:
Code:
su
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176
However, the extracted PIT-file can not be analysed using Pit Magic, whereas a downloaded pit-file of model i8260L could be analysed.
I think I only need a working PIT-file to get back on track.
Can somebody help me fix this phone again?
Thanks, Paul

@pamenja
hello .
i've no pit for I8260 but one for I8262 and pit partition is in : mmcblk18
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so you can try :
su
dd if=/dev/block/mmcblk18 of=/sdcard/out.pit bs=8 count=580 skip=2176
file size is 3,88 ko
regards

yakapa40 said:
you can try :
su
dd if=/dev/block/mmcblk18 of=/sdcard/out.pit bs=8 count=580 skip=2176
Click to expand...
Click to collapse
Hi yakapa40,
I tried this to no avail. Then in went to \dev\block\ and found mmcblck0p18. Tried that. Still Pit Magic could not analyze the file.
in \dev\block\ I found mmcblk0p1 to mmcblck0p24. So I tried each:
Code:
dd if=/dev/block/mmcblk0p[B]18[/B] of=/sdcard/out[B]18[/B].pit bs=8 count=580 skip=2176
No luck. Any ideas?

if you have a file size 5ko or less post it and i'll try to extract it with my tools

yakapa40 said:
if you have a file size 5ko or less post it and i'll try to extract it with my tools
Click to expand...
Click to collapse
the one from mmcblck0p18 is 5 ko. But in Notepad++ it only shows many NULs.
I would like to attach this file, however I cannot find a button 'insert file/attachment' or any such thing.
So how to post it?
I shared it through Google Drive
.....another thing: I can open ARUBA_SLIMSS_LTN_0125.pit in Notepad++ and I find hidden.img.ext4 and other partitions.
However, in none of the extractions I did could I find ext4.

I think I have found it.
I tried this:
su
dd if=/dev/block/mmcblk0p19 of=/sdcard/out19.pit
Click to expand...
Click to collapse
this resulted in a file which I could analyze with Pit Magic
I am trying it now. But updated my google drive.
I will give some feedback tomorrow.

yes it's the right file :
my errors : pit size is 242496 - 241472 = 1096 blocks = 512 Ko
mmcblk0p1 = idx0 so /mmcblk0p19 = idx18
i can open the file and it's the same as GT-I8262 but not same signature at the end
g
about the file size 512ko :

yakapa40 said:
yes it's the right file :
my errors : pit size is 242496 - 241472 = 1096 blocks = 512 Ko
mmcblk0p1 = idx0 so /mmcblk0p19 = idx18
i can open the file and it's the same as GT-I8262 but not same signature at the end
Click to expand...
Click to collapse
Thank you for your help!
Is having a different signature a problem?
I ask this because in Odin the GT-I8260.pit hangs, but the ARUBA_SLIMSS_LTN_0125.pit continues.
Only after ARUBA_SLIMSS_LTN_0125.pit Odin says it was a success. But on reboot the phone says that I have to get a firmware through Kies. But Kies says I can't (not official software).

Another try. The file size of GT-I8260.pit (512 kb) was about ten times bigger than that of the ARUBA_SLIMSS_LTN_0125.pit (4kb)
So I opened GT-I8260.pit in Pit Magic, and saved it as GT-I8260b.pit, which resulted in a file with size 4kb.
Odin does not hang with B]GT-I8260b.pit[/B].
However on boot the phone shows:
"Firmware upgrade encountered an issue. Please select recovery in Kies and try again"
This was with the unpacked I8260XXAPA1_I8260PHNAPA2_PHN.zip from SamMobile.
See https://www.sammobile.com/firmwares/galaxy-core/GT-I8260/PHN/
So I tried the earlier version: I8260XXAMG2_I8260PHNAMG1_PHN.zip, with success!!
So, I updated my google drive, will keep the PIT-file there for some time maybe you can add it to the pit-files om sammobile?
Thank you so much for your help!!
(now I can try to setup this phone as a baby monitor )

@pamenja .
pit files are written in hexadzcimal so you can use an hex éditor to remove all zerro bits at the end and not the signature .
with pit magic you have also remove signature ( GT-I8260b.pit ) and since galaxy S3 you need it for flashing with ODIN
for more informations about pit files : https://forum.xda-developers.com/galaxy-s6/general/g920f-pit-file-banded-firmwares-t3118459
in post post 29 you can see how to decode it
so your pit file with signature and without zéroo bytes at the end is here : https://drive.google.com/file/d/13-VNCGO0Iq8idM965f24L-c_Kv8NKD7g/view?usp=sharing
best regards

[SOLVED] GT-i8260 Pit-file
@yakapa40 .
Thank you for point this out. I have learned a lot these couple of day. And will look at the mentioned post about pit files a bit more
As per your instructions, I have used a hexEditor to delete all zero-bytes at the end of my extracted pit file. And after that compared it to the one you provided, to which you added a signature. I am happy to report that your pit-file and mine were exactly the same
On the note, I wish you (and all other readers) a happy 2019!
Thanks again for your help!!
This post can be closed as far as I am concerned

De 6