[TinyCore RedPill Loader (TCRP)]

4 hours ago, adamadam said:

I have a problem with the network in ds3615xs it works for several hours then the server stops responding after disconnecting the network cable the server resets itself and works for a few hours fine.  my specification is Dell optiplex 9020 i5 4690 network card under construction bootloader detects Intel e1000e, but what makes me wonder is when I created a Windows virtual machine in dsm it pointed to the e1000 network card.  can anyone help?  I struggle with it for a few days to no effect

i don't know your configuration. i'm on vmware workstation under windows and dsm works both from vmdk and from physical usb drive. set the network card as bridged and exit from vmware. open the folder where virtual machine is stored. look for the vmx file and open it with notepad. search the line "ethernet0.virtualDev = "e1000"" and just add a "e" at the end, save and exit. should work as for me.

[TinyCore RedPill Loader (TCRP)]

@killseeker@synoxpe no. i didn't faced that error, sorry...

i'm on an asrock j4005m that boot only from uefi. obviously i disabled secureboot.

i've tried again with a different flash drive and it just works.

at this time, i wrote the "tinycore-redpill.v0.4.4.img" image with rufus on windows. then i started a virtual machine with linuxmint edge 20.3 cinnamon x64 installed and followed the same steps that i posted previously. you clearly have to change "my" /dev/sdb with the right path pointing your device.

[TinyCore RedPill Loader (TCRP)]

hi. first of all thanks @pocopico for this great tool.
finally i managed to create a uefi bootable flash drive. the steps are very easy but it took me about the whole day to figure out.

after writing redpill tc loader image to your flash drive, you need a linux machine to add the uefi boot.

in my case, i have a notebook with linux mint installed (latest edge edition).
assuming that my flash drive was /dev/sdb, this is what i've done:

1. Mount the filesystem:
   sudo mount -o umask=000 /dev/sdb1 /mnt
2. Write the MBR and install the grub files required for legacy BIOS boot on the drive:   (i don't know if this step is really needed but anyway it works)
   sudo grub-install --no-floppy --boot-directory=/mnt/boot --target=i386-pc /dev/sdb
3. Install /EFI/BOOT/BOOTX64.EFI and other grub files required to load grub from a 64-bit UEFI firmware:
   sudo grub-install --removable --boot-directory=/mnt/boot --efi-directory=/mnt --target=x86_64-efi /dev/sdb
4. Unmount the filesystem:
   sudo umount /dev/sdb1

after that, remove the flash drive and try it. for me, it worked at first try. no need to edit any other file.

credits go to https://github.com/ndeineko/grub2-bios-uefi-usb for this helpful page without which I would never have succeeded.