31 replies to this topic

[jamesboxy]

finally found the culprit.

use this entry

title Trinity Rescue Kit v3.4

kernel /trk3/kernel.trk vollabel=KINGSTON ramdisk_size=65536 root=/dev/ram0 vga=788 splash=verbose pci=conf1 trkmenu

initrd /trk3/initrd.trk

i have changed all letters of kingston from lowercase to uppercase ie "vollabel=KINGSTON" instead of "vollabel=kingston"

i noticed that the letters of volumelabel in pendrive is always capital. so instead of using small case letter we have to used uppercase letters.

Edited by jamesboxy, 03 December 2010 - 07:20 PM.

[juandecerro]

finally found the culprit.

use this entry

title Trinity Rescue Kit v3.4

kernel /trk3/kernel.trk vollabel=KINGSTON ramdisk_size=65536 root=/dev/ram0 vga=788 splash=verbose pci=conf1 trkmenu

initrd /trk3/initrd.trk

i have changed all letters of kingston from lowercase to uppercase ie "vollabel=KINGSTON" instead of "vollabel=kingston"

i noticed that the letters of volumelabel in pendrive is always capital. so instead of using small case letter we have to used uppercase letters.

yes, finaly it works ... mmmmmm but if the vollabel is other??
can not be ignored? just like the others isos?

Edited by juandecerro, 03 December 2010 - 08:03 PM.

[jamesboxy]

yes, finaly it works ... mmmmmm but if the vollabel is other??
can not be ignored? just like the others isos?

trinity is very rare case where volume label is used to find the device.
there are no other linux distribution which are using volumelabel to find the device.

for avira there is no such problem.

Edited by jamesboxy, 03 December 2010 - 08:15 PM.

[juandecerro]

trinity is very rare case where volume label is used to find the device.
there are no other linux distribution which are using volumelabel to find the device.

for avira there is no such problem.

ok ok.. thanks again, see you!!

[crazydrve]

Here is my entry - drive is using grub4dos

title Trinity Rescue Kit 3.4 default mode with text menu
kernel /Trk3/kernel.trk ramdisk_size=65536 root=/dev/ram0 vga=788 splash=verbose pci=conf1 trkmenu vollabel=TRK_3-4
initrd /Trk3/initrd.trk

title TRINITY RESCUE KIT 3.4 - Extra Menu options
configfile /Trk3/menu.lst

dir - TRK3 at root of drive. I used default label that is recommended. and it all works, drive recognized, etc.
-----------------
>>>captive
>>>pxelinux.cfg
>>>share
>>>pi
>pi.fr
>unpi.cfg
>unpi.fr

AUTORUN.INF
boot.cat
bootlogo.jpg
bootlogo.xpm.gz
disableautorun.exe
initrd.trk
isolinux.bin
isolinux.cfg
kernel.trk
memdisk
memtest.x86
menu.lst
mkpxelinux
pxelinux.0
syslinux
syslinux.cfg
syslinux.exe
trinity.ico
trkramfs
trspack-1_0.exe
trsrun-1_0.exe
trsrun-1_0-nq.exe
vesamenu.c32

Edited by crazydrve, 01 October 2011 - 07:33 PM.

[amvhd]

hi
i get the last picture of juandecerro (in the Previous page) when do this works:
create new > add button > property > T.. > booting iso image > copy my acronicetrue image (iso) to ISO_SOURCE folder then rename it to test.iso > config property > config generate menu
>config deploy menus > then paste the path of ISO_SOURCE folder then press deploy then simolate the result
but get the error of the saied above.
sara - pmedia:

where past your source code??

please help me

Edited by amvhd, 29 October 2011 - 06:55 AM.

[steve6375]

Trinity Rescue Kit v3.4 Build 372 using grub4dos (not ISO file) method can be found here. I have used a grub4dos environment variable and a separate menu.lst to keep the whole thing neater and easier to maintain http://www.rmprepusb...nity-Rescue-Kit