<p dir="ltr"><br>
On Oct 23, 2014 4:50 PM, "Ankur Sinha" <<a href="mailto:sanjay.ankur@gmail.com">sanjay.ankur@gmail.com</a>> wrote:<br>
><br>
> On Fri, 2014-10-24 at 06:18 +0800, Ed Greshko wrote:<br>
> > Google ZISD. Look at screen. See "GRUB and ZISD - Cool Solutions |<br>
> > Novell" as second entry.<br>
> ><br>
> > Click on link.<br>
> ><br>
> > <a href="https://www.novell.com/communities/coolsolutions/grub-and-zisd/">https://www.novell.com/communities/coolsolutions/grub-and-zisd/</a><br>
><br>
> I actually tried that - it didn't seem to work. Instead of one sector<br>
> with ZISD, now I have 2.<br>
><br>
> The post is from 2008 and is probably referring to legacy GRUB.<br>
><br>
> From the error I had posted earlier, I think GRUB2 leaves the sector<br>
> occupied by ZISD be.<br>
> --<br>
> Thanks,<br>
> Regards,<br>
> Ankur (FranciscoD)</p>
<p dir="ltr">The post is telling you how to move the bits manually. It's mostly relevant to admins migrating from the pre-2008 version of the software doing the writing, to the version that knows better. Since you said that GRUB is trashed after every Windows boot, I think it is safe to assume that any changes you make to these sectors will not persist. It doesn't matter if you're writing GRUB or zeroes or what. It probably happens on 'refresh' - ie on boot, on every network transition, and every hour or two in between. You probably have a little bluish circle in the Windows system tray; right click, hit "show properties" and dig around to verify.</p>
<p dir="ltr">Unless you can convince the uni IT to upgrade their [very outdated and anecdotally terrible] system management infrastructure, or block that functionality on your machine, I think you will have to put GRUB somewhere else.</p>
<p dir="ltr">Nice seeing you in a sane time zone for a change, Ankur :)</p>
<p dir="ltr">--Pete</p>