RPiTC2 beta 1.99 out! UPDATE -> NEW image beta3

[ch13f]

The beta3 works with the Win32DiskImager.

I tried it with beta3 and my sd card cant be broken.

You copied the Image with Win32DiskImager on your SD-Card and put it in your Raspberry PI?

Which Raspberry PI you use to test?

Yes i did that, i use a Raspberry 2
I dont get a Signal @ my screen

Same issue here.

Having latest Windows 10 Preview build.
Using Win32DiskImager. After writing img file of beta to two different SD Cards. Both Cards are inaccessible.

Windows is telling you that they are corrupt and Need Formatting.

If you rewrite Image 1.4 to both cards the SD Cards are ok and Windows can Access the Cards.

But Overall Raspberry will not boot with These SD Cards.

Maybe something wrong with Win32DiskImager running under Windows 10.

Btw. im just using a raspberrypi one model b.

At least I want to say thank you for this Project!

[Frank]

I installed the 1.99 beta 3 today. Cannot get the Citrix Receiver working. The Add Store Citrix icon does not work, no display at all. Neither can I add an account by specifying a Storefront server address.

I have the same issue and wanted to add some detail:

The Symbol appears in the left dock after the Installation , I can click on the Symbol, but no program is starting up.
I use a raspberry pi 2 and cannot compare to the first model.
localization is German with German Keyboard. DHCP-assigned IP, Keyboard, Mouse and HDMI monitor...
The raspberry has been updated to the current firmware.

Frank

[raba]

Hello,

I'm new in this project. I had installed RPiTC2_r1.99.beta3.img. Now I don't find "RPiTC builder". Where is it?

Thanks
Ralph

[Frank]

I installed the 1.99 beta 3 today. Cannot get the Citrix Receiver working. The Add Store Citrix icon does not work, no display at all. Neither can I add an account by specifying a Storefront server address.

I have the same issue and wanted to add some detail:

The Symbol appears in the left dock after the Installation , I can click on the Symbol, but no program is starting up.
I use a raspberry pi 2 and cannot compare to the first model.
localization is German with German Keyboard. DHCP-assigned IP, Keyboard, Mouse and HDMI monitor...
The raspberry has been updated to the current firmware.

Frank

Found the error.. this is due to mistypein a path.
It looks für the eula in /opt/Citrix/ICAClient//nls/en/eula.txt
creating that file solves the issue, though a correction of the path would be preferred in the final release

[admin]

I installed the 1.99 beta 3 today. Cannot get the Citrix Receiver working. The Add Store Citrix icon does not work, no display at all. Neither can I add an account by specifying a Storefront server address.

I have the same issue and wanted to add some detail:

The Symbol appears in the left dock after the Installation , I can click on the Symbol, but no program is starting up.
I use a raspberry pi 2 and cannot compare to the first model.
localization is German with German Keyboard. DHCP-assigned IP, Keyboard, Mouse and HDMI monitor...
The raspberry has been updated to the current firmware.

Frank

Found the error.. this is due to mistypein a path.
It looks für the eula in /opt/Citrix/ICAClient//nls/en/eula.txt
creating that file solves the issue, though a correction of the path would be preferred in the final release

Great! Thanks!

[squevill]

I installed the 1.99 beta 3 today. Cannot get the Citrix Receiver working. The Add Store Citrix icon does not work, no display at all. Neither can I add an account by specifying a Storefront server address.

I have the same issue and wanted to add some detail:

The Symbol appears in the left dock after the Installation , I can click on the Symbol, but no program is starting up.
I use a raspberry pi 2 and cannot compare to the first model.
localization is German with German Keyboard. DHCP-assigned IP, Keyboard, Mouse and HDMI monitor...
The raspberry has been updated to the current firmware.

Frank

Found the error.. this is due to mistypein a path.
It looks für the eula in /opt/Citrix/ICAClient//nls/en/eula.txt
creating that file solves the issue, though a correction of the path would be preferred in the final release

Thanks - that solved it for me.