Well, I also thought about that.
I am working on an DOS application I wanted to package into FreeDOS's
format by default.
My exe is using a file called cwsdpmi.exe but cwsdpmi.exe is actually a
renamed hdpmi32.exe. Normally I would assume to cd to the folder where
my app is inside and to start it
It looks like you want it more reliable... Sounds very reasonable.
Actually more pros (more easy for you, faster) then cons (file size).
As you have the most work with it,
do it.
-mr
Mateusz Viste schrieb:
> Hi people!
>
> So far, we have always used packaging sources and binaries differently
There is
- SSHDOS v0.95 November 25, 2003 and
- SSH2DOS v0.2.1 from April 23, 2006
Why the more recent version has a lower version number?
What are the differences?
There is also patch "ROM-DOS Sockets patch" from August 25, 2008, what
does it do?
-mr
Alain M. schrieb:
> Michae
Christian Masloch schrieb:
>> It's a client and not a network drive.
>
> So a network drive that shows you a directory of a network server would be
> no network client?
You can perhaps always call it client.
But network drive is only the right word if it works in background and
you get an addi
Eric Auer schrieb:
> Hi,
>
LFN for FAT and for NTFS are working stable in Linux. Could a FreeDOS
developer grab this free knowledge from Linux and improve DOSLFN this
>>> way?
>>> very unlikely. Linux drivers are too different from DOS kernel or DOS
>>> TSR to be useful
>> What about bri
Eric Auer schrieb:
> Hi!
>
>> Like I suggested an SFTP client using XMS or JLM.
>
> There are already SSH, SCP and SFTP 1 and 2 clients,
> called SSHDOS: http://sshdos.sourceforge.net/
It's a client and not a network drive.
-mr
-
The new and up to date and linked on freedos.org wiki seams to be
http://apps.sourceforge.net/mediawiki/freedos/index.php?title=Main_Page.
While when I google for "freedos wiki" I still find
http://wiki.fdos.org/. Can the old wiki be linked on freedos.org? It
still contains some informations. What
David C. Kerber schrieb:
>
>
>> -Original Message-
>> From: Jim Hall [mailto:jh...@freedos.org]
>> Sent: Tuesday, March 31, 2009 3:30 PM
>> To: freedos-user@lists.sourceforge.net
>> Subject: Re: [Freedos-user] patents - was: LFN in FreeDOS
>> kernel? - was: aimed compatibility?
>>
>
>
Well, it would be theoretically possible to implement something like
ext3 as most DOS applications use the filesystem API and not the disk
directly, them wouldn't recognize.
But this wouldn't be a good solution as there are still much more other
patents we might have not considered yet.
-mr
usul
Jim Hall schrieb:
> On Tue, Mar 31, 2009 at 2:08 PM, Michael Reichenbach
> wrote:
>> Eric Auer schrieb:
>>> Hi Michael,
>>>
>>> indeed, MS LFN started with version 7 (Win9x)...
>>>
>>>> What about FreeDOS kernel and LFN? Wouldn't
usul schrieb:
> By the way I must repeat the question "who would be theoretically sued?".
>
> I would think the end users.
>
> For Example:
> Companies that distribute new PCs with FreeDos installed.
> someone that sold FreeDos on a bootable USB
> Someone that sold and built CD for open source.
>
Ralf A. Quint schrieb:
>> Not the programmer of DOSLFN would be sued, also probable not the
>> hypothetical programmer for LFN in DOS-C.
>>
>> I think it's the distributor who would get sued and this is in this case
>> the responsible person for the website. (Fortunally also other people
>> are red
Ralf A. Quint schrieb:
>> However, I just care about laws in my own country (and the national ones).
>>
>> As I live in Germany I see no reason to ensure to follow all US laws (no
>> racism or whatever here, just the same way I do not ensure it for any
>> other country where I do not life).
>>
>> I
Eric Auer schrieb:
> Hi Michael,
>
> indeed, MS LFN started with version 7 (Win9x)...
>
>> What about FreeDOS kernel and LFN? Wouldn't it make sense
>> also to add LFN to the FreeDOS kernel?
>
> Yes but: The DOSLFN license does not allow it so you would
> have to re-implement LFN from scratch an
usul schrieb:
> I would expect this type of thinking to defeat the patent.
>
> So educate me why am I wrong. :)
Well, the final verdict gives always the court. Unfortunately not always
the logic wins.
(I haven't said anything about bribemoney!)
It also depends on the technical understanding of
Ralf A. Quint schrieb:
>>> >From that view it's not possible for non-cooperates (individual hobbyist
>> projects) to develop and publish software. You would always need a legal
>> department which is telling "it's ok to violate patents, if them are are
>> accusing us we will accuse them with out co
Eric Auer schrieb:
> Hi Michael,
>
> indeed, MS LFN started with version 7 (Win9x)...
>
>> What about FreeDOS kernel and LFN? Wouldn't it make sense
>> also to add LFN to the FreeDOS kernel?
>
> Yes but: The DOSLFN license does not allow it so you would
> have to re-implement LFN from scratch an
Christian Groessler schrieb:
> Hmm, talking to a SMB server probably is quite involved (I've tried
> to debug some samba problems in the past and the "probably" in the
> last sentence is wrong).
> But how about a new, simple, protocol to transfer directory information
> and files between hosts? No
>
>
>
> On Mon, Mar 30, 2009 at 3:46 PM, Michael Reichenbach
> wrote:
>> Christian Groessler schrieb:
>>> Hi,
>>>
>>>> If you want you can setup a FTP server on DOS running as
>>>> TSR in background.
>>>> http://www.u
Ok, now I got your point and must agree. :)
-mr
usul schrieb:
> mr,
>
>> Because you are not doing everything on pure DOS this makes your
>> development more worse? That's s strange mind.
>>
>
> :) I'm strange I admit that but thats not whyI think it would be
> cheating, you are coming from the
Christian Groessler schrieb:
> Hi,
>
>> If you want you can setup a FTP server on DOS running as
>> TSR in background.
>> http://www.unet.univie.ac.at/~a0503736/php/drdoswiki/index.php?n=Main.Servers
>
> ?? This is a completely different topic.
No, since you asked for connecting to file server
usul schrieb:
> But yeah I was thinking that I would "cheat" for some of the stuff
> for developing on FreeDos at first but later I would try and do everything
> I could inside.
Cheat? Which kind of?
Because you are not doing everything on pure DOS this makes your
development more worse? That's s
usul schrieb:
> But I can do that from another pc that i usually have next to me. but
> it would be nice to have a complete evironment.
And I have forgotten to say...
You are most likely much faster with browsing the web and mailing if you
use a modern computer, modern multi tasking operating sys
usul schrieb:
> Uli,
>
> I bought ORiNOCO Classic Gold PC Card.
> http://www.orinocowireless.com/products/wifi/client/goldpccard/index.html
> I know wireless is a risk but I checked in the documentation it had
> dos and linux drivers :)
> and I downloaded the ISO with all of that on it.
Well, wl
This is an interesting topic...
If you want you can setup a FTP server on DOS running as TSR in background.
http://www.unet.univie.ac.at/~a0503736/php/drdoswiki/index.php?n=Main.Servers
msclient is nice to mount a remote server into a DOS device letter,
unfortunately it's indeed a memory hog and
cleanzero schrieb:
> I was trying to using the flat assembler FASM on freedos, but it complains
> about missing DPMI services ? Is it possible in some way to use it ?
http://www.unet.univie.ac.at/~a0503736/php/drdoswiki/index.php?n=Main.DPMI
example: hdpmi32 -r
--
Christian Masloch schrieb:
>> LFN for FAT and for NTFS are working stable in Linux. Could a FreeDOS
>> developer grab this free knowledge from Linux and improve DOSLFN this
>> way?
>
> FAT and FAT32 are already supported by DOSLFN, even some CD-ROM
> filesystems are. NTFS is not supported by a
FreeDOS -
http://blogs.msdn.com/virtual_pc_guy/archive/2005/02/02/365232.aspx
ctmouse, shsucdx -
http://blogs.msdn.com/virtual_pc_guy/archive/2004/10/21/246136.aspx
--
___
Free
Blair Campbell schrieb:
>> Also according to
>> http://www.unet.univie.ac.at/~a0503736/php/drdoswiki/index.php?n=Main.Compatibility
>> it also seams doslfn is not the answer and needs bugchecking by a third
>> developer.
>
> Even kernel support would have some of those issues, it seems only
> "not
Christian Masloch schrieb:
>> Which kind of compatibility does FreeDOS aim for? I mean compatible with
>> which MS-DOS version? 6.22, 7.10, 8.00?
>
> As far as I can tell, 8.00 is the same as 7.10 plus some restrictions (I
> used to have a PC with Windows Me).
Yes, well 8.00 can load Win ME.
http:
Which kind of compatibility does FreeDOS aim for? I mean compatible with
which MS-DOS version? 6.22, 7.10, 8.00?
-mr
--
___
Freedos-user mailing list
Freedos-user@lists.sourcefo
alfio castorina schrieb:
> Hi, I want to install freedos on my Macbook Pro using VMWare Fusion. Problem
> is that after booting from the cd image and creating the C: partition after
> reboot I get the message "invalid operating system". I suspect that is due
> that Freedos has not been installed ye
Eric Auer schrieb:
> Hi Michael,
>
>> I have created a wikipage which describes how you can install FreeDOS on
>> NTFS with permanent and full read and write access. It's not directly
>> installed on NTFS, but inside an raw image. There is no need to change
>> the partition table or the bootsector
Eric Auer schrieb:
> Hi!
>
>>> Another thing will be a list of things to test...
>
>> Well, things like xmstest, memtest, idecheck
>
> Those are not kernel related as far as I remember.
Not related to kernel, but to hardware and base software. You can see if
the change has broken something in a
Eric Auer schrieb:
> Hi Michael!
>
>>> thanks for suggesting an automated compile-and-test-SVN farm
>>> of test computers, I guess part of the problem is that you
>>> typically compile DOS in DOS and DOS does not run cronjobs.
>>> Conceivably a smart Linux DOSEMU solution is possible but in
>>> th
Eric Auer schrieb:
> Hi Michael,
>
> thanks for suggesting an automated compile-and-test-SVN farm
> of test computers, I guess part of the problem is that you
> typically compile DOS in DOS and DOS does not run cronjobs.
> Conceivably a smart Linux DOSEMU solution is possible but in
> that case th
Michael Reichenbach schrieb:
> Eric Auer schrieb:
>> If some programs
>> only work in another DOS but not in FreeDOS, write about
>> that problem on the mailing list.
>>
>> Thanks :-)
>>
>> Eric
>
I was remembering this thread about compatibilit
Eric Auer schrieb:
>> I've read claims that it's Eric's fault that most of the remaining
>> kernel developers [have quit] now but I haven't read yet enough of
>> the old discussions to have an opinion on that.
>
> I probably contributed to frustrating developers of the
> unstable branch (Lucho / A
Christian Masloch schrieb:
> I would like to hear what other kernel developers think about this. Or, if
> Eric can't find any other active kernel developer, anyone else interested
> in DOS-C or the FreeDOS project too.
>
> Regards,
> Christian
Will all due respect I think that Eric over compl
Eric Auer schrieb:
> Hi Michael,
>
>>> I do not think we should use code reversed from MS DOS sorry.
>> I think that too but it's no problem to reverse engineer the
>> specification as long you write your own implementation from scratch.
>>
>> Also the linux guys reverse engineered for example the
Eric Auer schrieb:
> I do not think we should use code reversed from MS DOS sorry.
I think that too but it's no problem to reverse engineer the
specification as long you write your own implementation from scratch.
Also the linux guys reverse engineered for example the Windows
networking protocol
Christian Masloch schrieb:
>>> Could you please test whether aborting some other
>>> application (no COMMAND.COM type program) works in FreeDOS?
>> Yes, first he application will be terminated and then also the command
>> interpreter which results in the same bug.
>
> Well this shouldn't happen (a
Christian Masloch schrieb:
>>> Which application do you abort?
>> None. No joke. I just boot the pure kernel (no configuration files),
>> start escape and press F12 - in MS-DOS no crash - in FreeDOS crash.
>
> Well, do you load COMMAND.COM (or FreeCOM or whatever CLI)?
Indeed, sorry. "Pure" FreeD
Christian Masloch schrieb:
> Which application do you abort?
None. No joke. I just boot the pure kernel (no configuration files),
start escape and press F12 - in MS-DOS no crash - in FreeDOS crash.
> Does the crash always occur?
Yes.
> Does it show rather random characters or are
> they always
website: http://au.geocities.com/short_stop_pacific/freesoft/system.htm
look for ESCAPE / BREAK (documentation, binary and source)
it's an TSR which provides to quit any application, those without quit
button and also hanging applications.
In MS-DOS 7.1 with no config.sys/autoexec.bat it works.
W
Michael Horvath schrieb:
> I have PocketDOS installed on my PDA. It loads a bootable version of
> FreeDOS from a floppy disk image. I'm having trouble figuring out where
> AUTOEXEC.BAT and FDCONFIG.SYS are located on this disk. Where can I find it?
Until now I wasn't aware of the PocketDOS proje
Eric Auer schrieb:
> Hi Michael,
>
>> Do BIOS update 100 % step by step as the manual says. No experiments wit
>> h DOS versions, TSR's, boot medium (if you shall use legacy floppy then
>> do so). Otherwise you risk the BIOS update to fail as the developers did
>> not thought about your modified u
Do BIOS update 100 % step by step as the manual says. No experiments wit
h DOS versions, TSR's, boot medium (if you shall use legacy floppy then
do so). Otherwise you risk the BIOS update to fail as the developers did
not thought about your modified use.
Ok, well you can experiment if you have the
Eric Auer schrieb:
> Hi,
>
>> Okay. I would really like to use FreeDOS, preferrably the full-install CD,
>> and definitely with USB disk support. Problem is, the NIC in the computer I
>
> On modern PC, your BIOS already does USB disk support for you and DOS.
You mean USB legacy support (for stor
John Ames schrieb:
> Okay. I would really like to use FreeDOS, preferrably the full-install CD,
> and definitely with USB disk support. Problem is, the NIC in the computer I
> want to install it on (a 3Com 3C595-TX) does not appear to be recognized by
> either the default packet driver or the manuf
Booting without emm386 will work, to make emm386 to work you need the
correct excludes X= or I= but don't ask me further.
After you got it running tell us how well Virtual PC works for your DOS
apps / DOS games, how good is the soundblaster / vga / vesa
implementation? Perhaps I've tested it in pa
Johnson Lam schrieb:
> On Sun, 15 Mar 2009 21:05:15 -0300, you wrote:
>
> Hi,
>
>> But, It works only at some machines.
>
> I've tested many PC with my bootable USB stick.
>
> USB boot heavily depends on BIOS itself, if the BIOS of that PC sucks, you
> have no chance whatever how hard you try.
Hi!
Originally eltorito.sys was only designed to work for a boot sequence like:
BIOS -> CD-ROM with no-emulation bootloader (for example syslinux) ->
memdisk -> DOS -> eltorito.sys
eltorito.sys continues to use the BIOS to access the device.
I discovered that eltorito.sys can be also used for CD-
Blair Campbell schrieb:
Why isn't this CD-ROM auto detection used for menu entry 1, 3,4 and 5?
>>> I don't really understand the question... CD-ROM drivers are loaded
>>> for 1, 3, 4, and 5; XCDROM.SYS would be the CD-ROM driver.
>> But the other CD-ROM drivers, such as eltorito.sys are only l
Blair Campbell schrieb:
>> Why isn't this CD-ROM auto detection used for menu entry 1, 3,4 and 5?
>
> I don't really understand the question... CD-ROM drivers are loaded
> for 1, 3, 4, and 5; XCDROM.SYS would be the CD-ROM driver.
But the other CD-ROM drivers, such as eltorito.sys are only load i
I have created a wikipage which describes how you can install FreeDOS on
NTFS with permanent and full read and write access. It's not directly
installed on NTFS, but inside an raw image. There is no need to change
the partition table or the bootsector.
http://grub4dos.sourceforge.net/wiki/index.ph
Hi!
I have a question about the fdfullcd.iso. It's a bit unclear for me...
The menu:
1. Install to harddisk using FreeDOS SETUP (default)
2. FreeDOS Safe Mode (don't load any drivers)
3. FreeDOS Live CD with HIMEM + EMM386
4. FreeDOS Live CD with HIMEM only
5. FreeDOS Live CD only
In A:\config.
Eric Auer schrieb:
> Hi Blair,
>
>> I think using aspi.sys you can use cdrecord with it. Maybe I will
>> test it if I can get FreeDOS to boot on my laptop (1.0 CD kernel fails
>> to boot).
>
> Does the Rugxulo.googlepages.com kernel work? You can
> use the floppy images there to make boot CD / D
smkururu schrieb:
>
>
> Christian Masloch wrote:
>> Which partitions does Fdisk list on the hard disk? FreeDOS can only access
>> partitions of the FAT12/FAT16 or FAT32 type with a drive letter.
>>
>> Regards,
>> Christian
>>
> Thanks a lot guys, that solved the problem since all of my partiti
Michael Reichenbach schrieb:
> Bernd Blaauw schrieb:
>> Eric Auer schreef:
>>> mode: You could use the technology of Rayer's ROMOS
>>> which allows you to boot a FAT12 image directly from
>>> ROM. This image has only 1 FAT, so MS DOS 6 does not
>&g
Bernd Blaauw schrieb:
> Eric Auer schreef:
>> mode: You could use the technology of Rayer's ROMOS
>> which allows you to boot a FAT12 image directly from
>> ROM. This image has only 1 FAT, so MS DOS 6 does not
>>
> I wonder how large such expansion ROM images can be (64K? more?). The
> Coreboot
Christian Masloch schrieb:
>> On read-only media the 'set /e bootdevice=bootdev' will create an error
>> due to write protection. How this can be solved?
>
> Did you set the TEMP or TMP environment variable to a directory on a
> writable drive?
No, there is no writable device.
Well, I could in
Eric Auer schrieb:
> Hi Michael,
>
>> I need a variable %bootdevice% (or w/e) pointing to the current
>> session's boot device (A:\ or C:\).
>
> Nice :-)
>
>> Is there such a variable or can you tell me how to set
>> this variable automatic in batch?
>
> I do not remember one, but it is extreme
Eric Auer schrieb:
> Hi Japheth,
>
>>> also many things are running in background :)
>>> just ask Eric, Mateusz, Rugxulo, Blair, ...
>> That's probably one of FreeDOS's problems: there's
>> only one guy - I don't want to be more specific - who
>> forces all communication into private mails. This
>
Christian Masloch schrieb:
> Besides, I'm too egoistic to write or re-write major parts
> of something when this new version isn't accepted because it isn't tested
> enough. That was the case with the "unstable" DOS-C version 2037 (which
> had many features version 2036 and the upcoming 2038
Christian Masloch schrieb:
>> Note that this would mean that you have to find the sources
>> of ELTORITO.SYS - nu2.nu says it is now free / unmaintained
>> but sources are not yet public - and add ELTORITO and also
>> SHSUCDX into the kernel itself. Otherwise you will be able
>> to boot the kerne
Eric Auer schrieb:
> Hi,
>
>> "grub4dos without menu" as "generic" boot file for FreeDOS
>> is really unnecessary, unless you need CD-ROM no-emulation
>> boot support or a file of which only the first few sectors
>> are loaded. I'm sure someone writing Assembly and motivated
>> enough could add th
For demonstration purposes I created a fdos.bin. I would like to send it
to the list but I don't think sending files to the list will work or is
warm welcomed. It's a generic file you can use to chainboot finally
kernel.sys. If you want it tell me and I send it private.
In boot.ini you just need t
Eric Auer schrieb:
sys can write the FreeDOS bootsector into a file. Today I recognized
that my freedos.bin working on one harddisk did not work on another
harddisk after a simple copy...
>
>>> ... The DOS boot sector must contain information about
>>> properties of your FAT filesys
Eric Auer schrieb:
> Hi!
>
>> sys can write the FreeDOS bootsector into a file. Today I recognized
>> that my freedos.bin working on one harddisk did not work on another
>> harddisk after a simple copy.
>>
>> I know grub4dos as a bootmanager has a generic binary bootable file or
>> memtest+ also h
Hi!
sys can write the FreeDOS bootsector into a file. Today I recognized
that my freedos.bin working on one harddisk did not work on another
harddisk after a simple copy.
I know grub4dos as a bootmanager has a generic binary bootable file or
memtest+ also has.
Can you provide such a generic boot
Hi!
Let's assume the hardware is working well... At the same time suspect
the some [1]software may make trouble. The goal is to do some checks to
see that all DOS software is working like it should.
What do I mean with faulty [1]software?
- bad BIOS settings
- booted by a bogus bootmanager
- BIOS
kurt godel schrieb:
> I am somewhat confused. Freedos runs on fat32; does this mean that freedos
> can run any 32 bit console app?
Many answers already. Like said FAT16 or FAT32 are just filesystems,
them have nothing to do with which kind of binarys you can run.
FreeDOS can run 16 bit DOS applic
Eric Auer schrieb:
> Hi, related to the recent "dd" thread here, Rugxulo suggests:
>
>> If it helps, there has been a third-party PAE hack for
>> DOS/32A for a while now (src only, so untested by me):
>
> (dos32a is a drop-in replacement for dos4gw, useful for watcom c)
>
>> http://dos32a.narech
pcdos2k schrieb:
> i don't recommend creative SB pci cards for use in DOS. it's great in windows
> and linux, but it is a pain to setup in dos.
Only the setup is a pain? Rest ok?
> if you already have it, then go for it. here are two websites to help you
> setup your SBPCI:
>
> http://easymame
Hans schrieb:
>>> Hans schrieb:
>>> I think you are up against quite a difficult software task. The days of
>>> NE2000 compatible ethernet controllers are long gone (unless I am
>>> wrong?),
>>> so your best bet is to find the Linux driver and datasheets for your
>>> controller and see if you can m
Hans schrieb:
> Hi Bray,
>
> - Original Message -
> From: "Braden C. Roberson-Mailloux"
> To:
> Sent: Wednesday, February 04, 2009 10:12 PM
> Subject: [Freedos-user] TCP/IP Driver for EEEpc
>
>
>> First, a shout out to Hans, mr, and Mark for helping me install FreeDOS to
>> my EEEpc.
Eric Auer schrieb:
> Hi!
>
>> First, a shout out to Hans, mr, and Mark for helping
>> me install FreeDOS to my EEEpc. It's Alive!
I am glad to help. :)
>> Second, are the drivers required to run the TCP/IP stack
>> specific to the ethernet device in a computer?
You need a packet driver to use t
Eric Auer schrieb:
>>> Are old PCI slots compatible with the new ones?
>
> Yes. Actually for DOS, it does not even make a real
> difference whether you have PCI, AGP or PCIe. You
> only miss the extra speed of the latter with DOS.
>
This is a good topic...
I scare a bit to upgrade once to a ISA-
Santiago Almenara schrieb:
> Thanks for all your answers.
>
>>From all your mail, I understood this:
>
>- There is not such thing as "VESA audio"
Unfortunately...
>- SoundBlasters, especially SB16, are the common "de facto" for DOS
>system (I used to have an ISA one, so I won't be a
Eric Auer schrieb:
> Hi Skyler,
>
>> Sorry for jumping in at the last minute, but to encrypt
>> something in RAM, wouldn't you need an external hardware
>
> No, you can work as if you were swapping: The 386 and newer
> CPU allow you to flag memory areas as "not accessible" and
> trigger a call wh
Jonathan W. schrieb:
> Sorry for jumping in at the last minute,
You are welcome to add your comments at any point, that's a mailinglist
for? :)
-mr
--
Create and Deploy Rich Internet Apps outside the browser with Adobe(R
Eric Auer schrieb:
> Hi!
>
>>> If I wanted to protect my mona lisa, I would
>>> encrypt it and put the key in the first 640k
>>> where I can be sure the BIOS wipes them :-p
>> You can only encrypt the harddisk, not the RAM.
>
> Yes you can encrypt and/or compress RAM, but of
> course you get lowe
Eric Auer schrieb:
> Hi!
>
BIOS doesn't destroy to much
>>> Enough to destroy whatever you wanted to hide by rebooting.
>> I see you haven't try it yourself yet...
>> Don't you know the video with the mona lisa?
>> http://citp.princeton.edu/memory/media/
>
> If I wanted to protect my mona li
Eric Auer schrieb:
> Hi!
>
>> Recently I did expand my computer from 1 GB to 2 GB of RAM.
>
>> At minimal configuration, just with himem and emm386.
>
> Try updating to HIMEMX and JEMM386, but take care that those
> default to giving you as much RAM as possible, without trying
> to protect DOS a
Eric Auer schrieb:
> Hi, read before you write ;-)
>
>> BIOS doesn't destroy to much
>
> Enough to destroy whatever you wanted to hide by rebooting.
I see you haven't try it yourself yet... Don't you know the video with
the mona lisa?
http://citp.princeton.edu/memory/
http://citp.princeton.edu/
Eric Auer schrieb:
> Hi,
>
>> I always wanted to know this, couldn't find it on google.
>> Is it possible to switch from long mode back to let's say real mode?
>
> Probably yes, but very slow. Until people are able to have
> more than 64 GB RAM in their PC, using PAE is a lot faster
> and easier
Hi!
Recently I did expand my computer from 1 GB to 2 GB of RAM. Finally I
checked that it's running well with Memtest86+ V2.11. I am also pretty
sure that the harddisk can not be the problem as it's a mobile disk and
working on other configurations ok.
For now I found two strange behavior.
At
Eric Auer schrieb:
> Hi,
>
4 GB or even more in 64 bit are also interesting
>>> The BIOS int 15.87 lets you access the first 4 GB, if you
>>> want to access more than that, you have to do fancy stuff
>
>> I think basically I would need to switch the CPU
>> into long mode.
>
> No you would n
Eric Auer schrieb:
> Hi!
>
>> - I would like to read the whole RAM (mainly only 32 bit - 2 GB, but 4
>> GB or even more in 64 bit are also interesting) and write it into a raw
>> image (also called sometimes flat or .img).
>
> The BIOS int 15.87 lets you access the first 4 GB, if you
> want to ac
read the whole RAM (mainly only 32 bit - 2 GB, but 4
GB or even more in 64 bit are also interesting) and write it into a raw
image (also called sometimes flat or .img).
- Also interesting for disk cloning, reading a whole drive and storing
it as a raw image.
-mr
> Michael Reichenbach escrev
Thank you!
Is there also some documentation about the DOS part available?
What is the equivalent for /dev/mem or /dev/hda under DOS?
Jim Hall schrieb:
> On Tue, Feb 3, 2009 at 3:41 PM, Michael Reichenbach
> wrote:
>> Is there a port of dd for DOS?
>>
>
> http://www.
Is there a port of dd for DOS?
regards,
-mr
--
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive,
Works good, Thanks!
-mr
Eric Auer schrieb:
> Hi Michael,
>
>> I need a variable %bootdevice% (or w/e) pointing to the current
>> session's boot device (A:\ or C:\).
>
> Nice :-)
>
>> Is there such a variable or can you tell me how to set
>> this variable automatic in batch?
>
> I do not remem
Hi!
I need a variable %bootdevice% (or w/e) pointing to the current
session's boot device (A:\ or C:\).
Is there such a variable or can you tell me how to set this variable
automatic in batch?
regards,
-mr
--
Create and
And I must add, if you have a newer notebook without DOS-compatible
sound hardware then there is unfortunally no way to get sound to work.
-mr
Michael Reichenbach schrieb:
> Hi!
>
> Sorry, but I think depending on what you plan to do you will not have
> much fun in DOS with that ca
Eric Auer schrieb:
> Hi,
>
>>> was some effort to collect funds to make people like
>>> Japheth, Tom, Georg, Arkady (just examples!) do it.
>> You mean the thread in bttr?
>
> Yes. And I mean please mention ALL URLs in ONE easy to
> google in the list archive mail: DOS soundcard Wiki,
> VSB ponde
Eric Auer schrieb:
> Hi! Off-list reply from me:
>
> Basically most of the information can be summarized by
> giving the DevelSound and that other sound related URL
> in the drdoswiki, so maybe you could post those along
> with a summary of what can be found there in a mail to
> this thread here?
Eric Auer schrieb:
> Hi!
>
>> I am not using any kind of virtualization software for it.
>
> Okay so you use DOS in real hardware.
>
>> Do you think this card is also compatible with the Intel HDA ???
>
> Depends. Modern mainboards use HDA or AC97 for sound.
> Only modern DOS software like MPXP
Santiago Almenara schrieb:
> Thanks Alain:
>
> n Mon, Feb 2, 2009 at 1:01 PM, Alain M. wrote:
>
>> if you use VMware you will nedd another driver... VMware creates a
>> Virtual machine and that means that everything is virtual. Including
>> that your virtual machine will allways be the same rega
1 - 100 of 239 matches
Mail list logo
