Re: DOS doesn't work anymore!



"Ed Ferris" <pseudo@xxxxxxx> wrote in message news:Xns96C8DC31D9705edfcorecom@xxxxxxxxxxxxxxx
Hi folks. This is my first visit here, so my problem may have a well-
known fix, I hope.
My OmniBook started making burnt-plastic smells so I got a new laptop. I
have a large database programmed in QuickBasic 4.5. When I run QBasic
(off the Windows 98SE disk) under Command Prompt, it can't access any
files and quits on Bad File Mode error. I think this is because
everything in XP is NTFS.
So ...
1) Get Microsoft to fix their half-assed DOS emulator. Not likely.
2) Wipe the disk, format it as FAT32, and reinstall XP. What utilities
do this? -- not Disk Management or DiskPart as far as I can tell. Will
DOS apps read FAT32 files?
3) Make a FAT32 partition (how?), install another copy of XP in it. No
advantage over #2, I would think.
3a) Make a FAT32 partition and install Windows 98SE. Probably would
cause horrendous conflicts.
4) Make a FAT partition and keep the data files in it. Will XP
translate an NTFS file into FAT (or FAT32) when I move it into the new
partition?
5) Wipe the disk, trash XP, and install Linux. Their DOS emulator
works.
6) Find a still-working OmniBook and buy it cheap.


Any other (polite) suggestion?



The NT kernel never has allowed direct hardware access (except by privileged drivers). You didn't bother to mention what OS you had on your old computer to give a clue as to why your old program would work over there. The DOS *shell* you use in NT is NOT an emulator. It's just a console mode DOS *shell*. Sounds like you probably had DOS/Win9x-ME on your old computer and now you expect old programs that bypassed the OS and made direct hardware access to also work under an NT kernel.

Have you yet tried to use the compatibility mode? Start -> Help and Support, search on "compatibility mode". Might work, might not if your program is indeed trying to directly access the hardware. If none of the compatibility modes work, start looking into multi-booting of different operating systems where you use a boot manager, like BootMagic or BootIT NG. It's too late to think about dual-booting unless you know how to recover the system partition's boot sector where you installed Windows XP because a later install of Windows 9x/ME will overwrite it and make Windows XP unusable. Or you could use Virtual PC to use load a virtual instance of an old Windows 9x/ME to run your old program under it, but you'll need to make sure you have lots of memory so you can allocate enough to the guest OS(es) and to the parent OS.

--
____________________________________________________________
For e-mail, remove "NIX" and add "#LAH" passcode to Subject.
____________________________________________________________

.



Relevant Pages

  • Re: XP Upgrade install problem
    ... I have not been able to boot to Windows since the first reboot ... The CD won't run in DOS. ... I ran the Winnt file from DOS and the install went ok. ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Install Firefox questions
    ... > I would recommend to you that you wait for your harddisk and install SuSE ... I downloaded using Windows ... LINUX was in 1996 when I had a triple boot system (DOS, LINUX, and ... I never crashed DOS except once intentionally, ...
    (alt.os.linux.suse)
  • Re: XP Upgrade install problem
    ... To start the Windows XP installation boot the computer *with* the XP CD-ROM, stick the cd in the drive and restart the computer. ... As you probably already know, Windows NT/2000/XP/Vista are pure 32-bit operating systems, there is no 16-bit DOS in those operating systems, any 16-bit applications running on these pure 32-bit operating systems must be run inside a 16-bit Virtual Machine. ... after the screwed up Install. ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Clean Install Windows XP
    ... > I got a Windows XP Home Original CD. ... > should I clean install XP or upgrade. ... I also wana convert to NTFS partition if its ... FAT32 vs NTFS.. ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: dos foxpro 2.6 app freezes on Windows 2003 server
    ... What I'm about to do though, as a final resort, is to install SP1 Beta. ... > FoxPro for DOS 2.5 system which we have had to migrate from a Windows ... Because the new network is not allowed DOS ... > was to be a Windows 2003 server. ...
    (microsoft.public.win2000.termserv.apps)

Loading