SliTaz SliTaz Forum

You are not logged in.

#1 2012-03-29 15:44:37

wanting2learn
Member
Registered: 2012-03-29
Posts: 7

Failed to execute /init error. when launching my iso.

I have followed the steps here to try and build myself a Slitaz system in order to help me learn more about linux.

http://doc.slitaz.org/en:scratchbook:base-system

After the first of this tutorial page I tried to launch my iso using VMWare player.

When I started my version of slitaz I got the welcome screen asking me to <Enter> to boot.

When I hit enter I get the a Failed to execute /init error.

Please see the attached image.

What could be wrong here????

Thanks

Offline

#2 2012-03-29 15:50:24

wanting2learn
Member
Registered: 2012-03-29
Posts: 7

Re: Failed to execute /init error. when launching my iso.

I have checked and I see that my slitaz-cooking.iso is only 3.27 MB.

What size should it be??

Offline

#3 2012-03-29 17:09:22

tux61
Member
Registered: 2012-02-29
Posts: 13

Re: Failed to execute /init error. when launching my iso.

34,5 Mo on http://mirror.slitaz.org/iso/cooking/slitaz-4.0-RC3.iso

Offline

#4 2012-03-29 17:32:35

mojo
Administrator
Registered: 2011-03-29
Posts: 2,174

Re: Failed to execute /init error. when launching my iso.

@wanting2learn

Every iso slitaz offers for download has a md5sum verification file to determine if the iso which is downloaded is an exact match of the same iso on the server. If your using windows download the iso and it's matching .md5 file,open  the .md5 in notepad to see the hash number.

Run the downloaded slitaz iso through this program: http://www.winmd5.com/

If the hash of the slitaz iso doesn't match the hash in it's .md5 file the download is corrupt or incomplete.

Redownload the slitaz iso and reverify until the iso and md5 match.

A VMX has to be created before the iso will run on vmware player.

http://easyvmx.com/tutorial.shtml

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]