MSR113@psuvm.psu.edu (Matthew Starr Richmond) (09/04/90)
I don't know if this has been discussed before, so please forgive my ignorance if it has... I currently have 2 megs total RAM on an AT 286, and I'd like Windows 3.0 to be able to use all of it. Now am I correct in assuming that it must use HIMEM.SYS to do this? I do install it as a device driver in CONFIG.SYS, but it says only 64k is used..? Is there some switch I can set to make it the whole 2 megs? On another note, is there a way to draw/create new icons? Or perhaps an FTP site where there are some? Any and all help will be greatly appreciated.. ************************************************************************ * Matthew S. Richmond * * __ ______ , __ __ MSR113@PSUVM.PSU.EDU * * ( / /| /__) /__) * * \ / /_| /\ /\ MSR113%PSUVM@PSUVAX1.UUCP * * .__) / / | / \ / \ * ************************************************************************
palm@admin.kth.se (Christer Palm) (09/04/90)
In article <90246.150126MSR113@psuvm.psu.edu> MSR113@psuvm.psu.edu (Matthew Starr Richmond) writes: >I don't know if this has been discussed before, so please forgive my >ignorance if it has... >I currently have 2 megs total RAM on an AT 286, and I'd like Windows >3.0 to be able to use all of it. Now am I correct in assuming that >it must use HIMEM.SYS to do this? I do install it as a device driver >in CONFIG.SYS, but it says only 64k is used..? Is there some switch >I can set to make it the whole 2 megs? HIMEM.SYS has to be in CONFIG.SYS Use Program Manager funktion About Program Manager in the Help meny. It vill state Windows mode and free memory and memory in use. Windows finds your memory all by itself if HIMEM.SYS are installed. If you are using SMARTDRV.SYS HIMEM.SYS has to be installed first. I think HIMEM.SYS is using 64k thats all. /Christer
pwilcox@paldn.UUCP (Peter McLeod Wilcox) (09/06/90)
HIMEM.SYS does two things (actually three), first it makes available as a requestable resource the first 64k segment after 1meg, i.e. with a 80286 or better, the segment address FFFF does not wrap around to 0 like it does on an 8086. The second function is to allocate and move blocks of extended memory, the user requests a block of extended memory and receives a handle, the handle is then used to access the extended memory via himem.sys. The third function is controling the A20 address line (enable and disable) in a hardware independent fashion, which it needs to do to perform the other two functions. Note that none of this is useful unless the program being run knows how to access the XMS driver, which very few programs do. -- Pete Wilcox ...gatech!nanovx!techwood!paldn!pwilcox
kperson@plains.NoDak.edu (Kerry Person) (09/06/90)
In article <90246.150126MSR113@psuvm.psu.edu> MSR113@psuvm.psu.edu (Matthew Starr Richmond) writes: ... stuff deleted >On another note, is there a way to draw/create new icons? Or perhaps >an FTP site where there are some? >Any and all help will be greatly appreciated.. >************************************************************************ >* Matthew S. Richmond * There is a great icon drawing application called icondrw.zip. I have found it on cica.cica.indiana.edu in directory /pub/pc/win3/icons. Kerry Person kperson@plains.NoDak.edu
mcdonald@aries.scs.uiuc.edu (Doug McDonald) (09/08/90)
In article <269@paldn.UUCP> pwilcox@paldn.UUCP (Peter McLeod Wilcox) writes: >HIMEM.SYS does two things (actually three), first it makes available >as a requestable resource the first 64k segment after 1meg, i.e. with >a 80286 or better, the segment address FFFF does not wrap around to >0 like it does on an 8086. > >The second function is to allocate and move blocks of extended memory, >the user requests a block of extended memory and receives a handle, >the handle is then used to access the extended memory via himem.sys. > >The third function is controling the A20 address line (enable and disable) >in a hardware independent fashion, which it needs to do to perform the >other two functions. > >Note that none of this is useful unless the program being run knows >how to access the XMS driver, which very few programs do. >-- However, there is a FOURTH function, that DOES affect programs that don't know to access himem.sys's particular scheme: It prevents them from accessing extended memory using the previosly defined standards - the bios calls and VCPI. In other words, himem.sys breaks many, many programs. This was dumb. Doug McDonald