On Thu, Apr 09, 2015 at 11:13:58AM +, Marcin Cieslak wrote:
> On Thu, 9 Apr 2015, Slawa Olhovchenkov wrote:
>
> > On Wed, Apr 08, 2015 at 03:30:41PM -0400, Ryan Stone wrote:
> >
> > > I've been playing around with trying to set one only slice as active to
> > > make the loader boot it, but i
On Thu, 9 Apr 2015, Slawa Olhovchenkov wrote:
> On Wed, Apr 08, 2015 at 03:30:41PM -0400, Ryan Stone wrote:
>
> > I've been playing around with trying to set one only slice as active to
> > make the loader boot it, but it appears that doesn't actually work.
> > boot0cfg would cover half of the us
e tests are all FreeBSD-based while the OEM is Windows 95 based. I
> need to come up with a way to integrate them together.
>
> We're looking at dual-booting FreeBSD and Win95. We're thinking of booting
> into Win95, the OEM can do their thing, switch to booting FreeBSD, run
On Wed, Apr 08, 2015 at 03:30:41PM -0400, Ryan Stone wrote:
> I've been playing around with trying to set one only slice as active to
> make the loader boot it, but it appears that doesn't actually work.
> boot0cfg would cover half of the use case (switching from FreeBSD back to
> Win95), but I'm
... why's stuff have to be complicated?
Win95 has minimal if any boot sector protection. Just go look at what
boot0cfg does, figure out which sector you have to read/modify/write,
and do that.
Of course, I'd also check first to ensure it's updating a freebsd
bootblock, or you may render a non-dua
On Wed, Apr 8, 2015 at 12:30 PM, Ryan Stone wrote:
>
> We're looking at dual-booting FreeBSD and Win95. We're thinking of booting
>
Wow, I like your problem. It's really weird, and I like weird problems. :)
Since you are looking at automating a complicated process,
he
On Wed, Apr 08, 2015 at 08:09:42PM +, Marcin Cieslak wrote:
> On Wed, 8 Apr 2015, Slawa Olhovchenkov wrote:
>
> > On Wed, Apr 08, 2015 at 03:30:41PM -0400, Ryan Stone wrote:
> > 4. (optional) create windows95 boot.ini for fail back load FreeBSD
>
> http://support.microsoft.com/en-us/kb/15799
On Wed, 8 Apr 2015, Slawa Olhovchenkov wrote:
> On Wed, Apr 08, 2015 at 03:30:41PM -0400, Ryan Stone wrote:
> 4. (optional) create windows95 boot.ini for fail back load FreeBSD
http://support.microsoft.com/en-us/kb/157992
I think boot.ini comes with ntldr, and Win95/98 started DOS-like..
//Marc
e tests are all FreeBSD-based while the OEM is Windows 95 based. I
> need to come up with a way to integrate them together.
>
> We're looking at dual-booting FreeBSD and Win95. We're thinking of booting
> into Win95, the OEM can do their thing, switch to booting FreeBSD, run
th a third-party OEM's process. My employer's
> hardware tests are all FreeBSD-based while the OEM is Windows 95 based. I
> need to come up with a way to integrate them together.
>
> We're looking at dual-booting FreeBSD and Win95. We're thinking of booting
>
tests are all FreeBSD-based while the OEM is Windows 95 based. I
> need to come up with a way to integrate them together.
>
> We're looking at dual-booting FreeBSD and Win95. We're thinking of booting
> into Win95, the OEM can do their thing, switch to booting FreeBSD, run
ws 95 based. I
> need to come up with a way to integrate them together.
>
> We're looking at dual-booting FreeBSD and Win95. We're thinking of booting
> into Win95, the OEM can do their thing, switch to booting FreeBSD, run our
> tests and produce a .csv file with t
On Wed, 8 Apr 2015, Ryan Stone wrote:
> No, this isn't a late April Fools joke. :(
>
>
> We've discussed just switching hard drives, but we really want to shoot for
> a 100% automated process. Anybody have any ideas?
I guess due to hardware interfacing virtualization is not an option?
I've see
h a way to integrate them together.
We're looking at dual-booting FreeBSD and Win95. We're thinking of booting
into Win95, the OEM can do their thing, switch to booting FreeBSD, run our
tests and produce a .csv file with the results, and then boot back into
Win95 for them to finish
14 matches
Mail list logo
