Koozali.org: home of the SME Server

Obsolete Releases => SME Server 7.x => Topic started by: markfarey on February 17, 2006, 01:25:26 PM

Title: Version 7 ISO installation problems
Post by: markfarey on February 17, 2006, 01:25:26 PM
Can anyone please explain the difference between the ISO image file named "smeserver-7.0pre3.iso" and "smeserver.iso" in the download area?

I have downloaded and burned the former, but it will not boot on my Linux box, but will on an old PC. I consistently get a CDROM error at boot time. I think my BIOS is configured correctly, but maybe it's being "picky".

Any advice will be greatly appreciated.

Mark.
Title: Version 7 ISO installation problems
Post by: chris burnat on February 17, 2006, 01:58:42 PM
Mark,  Please report this problem to the bugtracker, give as much information as possible.  There was a booting issue with the previous version (pre2.iso), however, this has been fixed.  You can access the Bugtracker using the links on the left of the screen, you may need to register, not a bg deal...  Many thanks.
Title: Version 7 ISO installation problems
Post by: Reinhold on February 17, 2006, 03:07:01 PM
mark,

(as in many other places)

__________The current iso is (always) called:__________  
Code: [Select]
smeserver.iso

... as of today Feb. 17 2006 that would be "smeserver-7.0pre3.iso"
tomorrow (or some time later) that might be "smeserver-7.0pre4.iso"
You can check looking at size and md5.

As to bugs: Please follow burnat's advice.
Make sure the .iso files .md5sum checks out correctly (check for bad download)
I always use the "on CD check" in addition (check for bad burn)

Regards
Reinhold
Title: Version 7 ISO installation problems
Post by: gordonr on February 17, 2006, 10:50:19 PM
Quote from: "Reinhold"
mark,

(as in many other places)

__________The current iso is (always) called:__________  
Code: [Select]
smeserver.iso

... as of today Feb. 17 2006 that would be "smeserver-7.0pre3.iso"
tomorrow (or some time later) that might be "smeserver-7.0pre4.iso"
You can check looking at size and md5.

We do this for two reasons: you can always grab smeserver.iso and get the latest, and it means our mirror sites only need to sync up the changes, reducing mirror propogation time and bandwidth. If you use rsync or zsync to grab the latest image, you can do the same.