Op 19-5-2011 2:28, Alain Mouette schreef:
> I managed to make a Boot CD that works almost in all machines. The only
> one that is not working is "Virtual PC 2007". it locks uppun execution
> of JEMM386 from a CD image. XMGR is used because it is required by UIDE.
Technically UIDE doesn't require X
Hi Japheth,
I am glad that you are here, it is nice to have our little family
mantaining contact.
I managed to make a Boot CD that works almost in all machines. The only
one that is not working is "Virtual PC 2007". it locks uppun execution
of JEMM386 from a CD image. XMGR is used because it i
> 1). NOEMS is rarely used, and a lot of things don't handle it well.
...
> ... I wouldn't do this. Just load a XMS
> driver only (and not via "NOEMS").
NOEMS is ok and safe, the switch which causes problems with some programs is
FRAME=NONE.
> 2). Actually, I've noticed JEMM386 will hang if you
Thanks to all of you that have helped me with this problem. It could
have taken ages to test and understand what was happening...
Many Thanks to Eric Auer who had a LOT of patience with me, I manage to
make it run. So here is my minimalistic setup. I hope that someone can
publish it somewhere.
On Tue, 2011-05-17 at 19:04 +0200, Bernd Blaauw wrote:
> JEMM is at 5.74
Thanks for that one, switching to JEMMEX just solved a problem where
Bochs would barf if EMM386.EXE was loaded.
--
Tactical Nuclear Kittens
--
Alain et al,
>> I do need as much conventional memory as I can get, and even the it is a
>> tight fit...
>>
>> So everyone belives that
>> JEMM386 X=TEST NOEMS
>> is safer? if so, I will change...
>
> My point was that ACPI tables (and/or too aggressive searching by FD
> [J]EMM386?) makes it ne
Op 17-5-2011 20:41, Alain Mouette schreef:
> Well, so it is a BIOS bug, and that is the end of research in this
> direction...
>
> Either syslinux (that seems to be better but for which I need help) or
> RDISK+SUBST (that I know, but may be a bit clumsy)
ok, made a very basic ISO generation batchf
Hi,
On Tue, May 17, 2011 at 3:15 PM, Alain Mouette wrote:
> (top posting to make it shorter)
>
> I do need as much conventional memory as I can get, and even the it is a
> tight fit...
>
> So everyone belives that
> JEMM386 X=TEST NOEMS
> is safer? if so, I will change...
My point was that ACP
Op 17-5-2011 20:41, Alain Mouette schreef:
Alain, can I privately send you a complete disk image sometime tomorrow
by email? Would be 1.44MB, maybe slightly smaller if compressing first.
It would replace your own floppy image directly, you can still use your
own method of ISO generating.
Basicly
Hi Alain,
> (I hope this messags comes though, 5th try...)
One got automatically blocked because it had a (too big)
attachment, and I think that is good. I see you already
transferred the same information without attachments :-)
Eric
---
Jack,
>> ==>> so, imho, the drive A: is disapearing when UIDE is loaded. It looks
>> like an interaction between the BIOS boot driver that creates A: for the
>> CD boot image and UIDE :(
>
> I wrote UIDE to be a "standard" system driver, not a "CD boot" driver,
> and I was unaware that BIOS "CD
(top posting to make it shorter)
I do need as much conventional memory as I can get, and even the it is a
tight fit...
So everyone belives that
JEMM386 X=TEST NOEMS
is safer? if so, I will change...
Thanks,
Alain
Em 17-05-2011 16:35, Rugxulo escreveu:
> Hi,
>
> On Tue, May 17, 2011 at 10:45
> You can also
> run "JEMM386 LOAD" at any time but that doesn't give you UMBs.
A program modifying DOS's internal data which could effectively link in
new UMBs is easy enough to write, provided that the kernel's handling of
the UMA is compatible enough to that of the MS-DOS kernel.
Regards,
Hi,
On Tue, May 17, 2011 at 10:45 AM, Alain Mouette wrote:
>
> I am encountering a strange problem with UIDE. It happens with some
> machines but not all, one of the failing machine is nearby so I can make
> more tests easely...
>
> I am using UIDE and XMGR from 10-May-11, I made my config from y
Well, so it is a BIOS bug, and that is the end of research in this
direction...
Either syslinux (that seems to be better but for which I need help) or
RDISK+SUBST (that I know, but may be a bit clumsy)
Thanks,
Alain
Em 17-05-2011 15:05, Jack escreveu:
>
> Alain,
>
>> I just foud how to make it
Em 17-05-2011 14:04, Bernd Blaauw escreveu:
>
> I've recently encountered the same issue, not sure if it's purely
> limited to booting from CD-ROM.
> In my case I tend to use Syslinux --> Memdisk --> Disk Image ( -->
> bootsector --> kernel --> config.sys --> shell --> autoexec.bat -->
> com
Em 17-05-2011 14:02, Tom Ehlert escreveu:
> Hi Alain,
>
> most likely UIDE disturbs the BIOS boot drive emulation
> I have no idea if UIDE can work around this.
>
> you can work around this by
>
> create a virtual disk
> copy A: to virtual disk (including autoexec.bat)
> so that A: is
Alain,
> I just foud how to make it work (kind of...)
>
> I boot normally, single-stepping, loading all *except UIDE*, than I do:
>SET COMSPEC=C:\COMMAND.COM (it's the same)
>C:
>DEVLOAD A:\DOS\UIDE.SYS /D:CDROM
>
> it loads, and I can access drive C:, but if I access A: it locks ju
Op 17-5-2011 19:40, Alain Mouette schreef:
> I boot normaly, single-stepping, loading all *except IEDE*, than I do:
> SET COMSPEC=C:\COMMAND.COM (it's the same)
> C:
> DEVLOAD A:\DOS\UIDE.SYS /D:CDROM
>
> it loads, and I can access drive C:, but if I access A: it locks just
> the same
Hi Bernd, Hi Jack,
Em 17-05-2011 14:04, Bernd Blaauw escreveu:
> Op 17-5-2011 17:45, Alain Mouette schreef:
>> I am using UIDE and XMGR from 10-May-11, I made my config from your
>> example (whole file attached), jemm386 is 572 dated 13mar2008 (complete
>> config at the end):
>> device=a:\dos\xmgr
Hi Alain,
most likely UIDE disturbs the BIOS boot drive emulation
I have no idea if UIDE can work around this.
you can work around this by
create a virtual disk
copy A: to virtual disk (including autoexec.bat)
so that A: is no longer needed
execute autoexec.bat from virtual disk
Op 17-5-2011 17:45, Alain Mouette schreef:
> I am using UIDE and XMGR from 10-May-11, I made my config from your
> example (whole file attached), jemm386 is 572 dated 13mar2008 (complete
> config at the end):
> device=a:\dos\xmgr.sys /B
> device=a:\dos\jemm386.exe I=TEST NOEMS
> device=a:\dos\xmgr.
Hi Jack,
(I hope this messags comes though, 5th try...)
I am encountering a strange problem with UIDE. It happens with some
machines but not all, one of the failing machine is nearby so I can make
more tests easely...
I am using UIDE and XMGR from 10-May-11, I made my config from your
example
23 matches
Mail list logo
