• Please review our updated Terms and Rules here

Dave Dunfields Imagedisk

Whenever I have had problems with IMD, it has always turned out to be either a BIOS limitation, a BIOS setting or a resource conflict. In your case, I would guess possibly a resource conflict between FDD and HDD drivers - perhaps DMA? It shouldn't happen on default settings, but might happen if there are any tweaks to BIOS or DOS configuration that IMD does not recognise.

Rick
 
I've had a look at the boot diskette that Frank made after the one I suggested. There are issues--I wonder if his COMMAND.COM is correct or infected. IO.SYS and MSDOS.SYS match. When I replace the COMMAND.COM, IMD still hangs as Frank mentions. I haven't gone much farther than that, other than wondering if something's been corrupted inadvertently.

I sent him an image of the boot disk that I use (DOS 6.22 also), so he can compare and contrast.
 
The disks image you sent me (md622imd) seems to check out mostly ok. The boot sector seems normal, the IO.SYS, MSDOS.SYS, COMMAND.COM, HIMEM.SYS, and RAMDRIVE.SYS match what I have on a set of 6.22 setup disks.

There is one odd thing, however. There is a copy of Drvspace.bin that seems to be from a beta version of Windows 95 (3/2/95?). Try deleting that and see if that makes a difference.
 
The DRVSPACE.BIN was placed on my diskette by the FORMAT /S command. I'll double-check my installation source, but I believe it was the MSDN distro for DOS 6.22.
 
Wait, I'm confused now. chromedome/Frank which image did you send me? One you created that didn't work on your machine, or the one chuck created that you say did work?
 
Ok, got your disk image. Both command.com and imd.com are infected with the "athens" virus:

Code: 
Virus data file  V220 created 03/30/95   2:39:50
No viruses found in memory.
Scanning A:
A:\COMMAND.COM
        Found the ATHENS virus
A:\TEST\IMD.COM
        Found the ATHENS virus
                                                                              
Summary report on A:

File(s)
        Analyzed: ..............      11
        Scanned: ...............       7
        Possibly Infected: .....       2
Master Boot Record(s):..........       1
        Possibly Infected:......       0
Boot Sector(s):.................       1
        Possibly Infected:......       0


Time: 00:00.07

You should assume any files/disks these programs have come in contact with are also infected.
 
Well that sucks. Reformat my DOS system again! Just wonder were they came from? Someguy: What virus scanner did you use. Could be on my main system. I am using AVG 2013.
 
I used a shareware DOS version of McAfee's virus scanner dated 3-31-95 that I had sitting on my DOS machine. I just double checked, and the good news is that it appears that running McAfee scan with the /CLEAN option several times seems to remove the virus (but some files might remain damaged). The MS scanner bundled with DOS 6.22 might also be able to do the same thing.

Just to test, I threw the infected files at a VM that also has AVG2013, and it set AVG off. But the only thing AVG knows to do with the infected file is outright delete it. Of course AVG won't look inside disk images.
 
Update finally got it to run off of hard drive. Used my seldom used DOS 6.00 disks to format C: & install DOS and make the IMD directory. Copied IMD 1.17 and the .IMD images and works like a charm....So far!
 
Chromedome45 said:
OK to all those peeps that have it working could you provide a hardware listing of the system you are running it on. Ok Need Computer type and if it is a commercial system built system with CPU and CPU speed, Ram amount, are you using the integrated floppy controller or an external floppy card. If a homebrew system what motherboard ETC and all pertinent info as listed above. This would help me out a lot.

In a pervious post I mentioned I tried on several systems with no luck. So any info appreciated.
Click to expand...

This. Please.
I'm trying to rock all my imaging work form a Compaq Portable 386 and it would be awesome to know if my own problem is either something not being configured or if I'm up against a limitation in the controller/the high density drive not translating. Every osborne CP/M image so far is not bootable even though imgdisk is apparently successfully writing disks.

I made a similar system using a clone for a previous employer. It's way more handy than lugging around an entire desktop system.
 
You probably want to run Dave Dunfield's testfdc program to make sure you can actually write single-density floppies with your Compaq Portable, assuming you're writing single-density Osborne 1 disks. Many PC controllers won't do single-density at all, and most won't write single-density "360K" media on a 1.2 MB 5.25" drive.
 
I'm using a AHA-1542cp ISA SCSI controller in my system. It handles single density with no problems. Just had to disable the onboard floppy controller. My system is a Pentium 1 233MHz. Unless your Compaq has an ISA bus. Then you can use this type of controller instead of the onboard floppy. Just run setup and disable the onboard controller. And if you have access to one of those Compaq 1/3 height 5.25 360K drives install it instead.
 
If this will help anyone, I have ported all the imagedisk utilities (programs that do not access the disk controller) to Linux. Dave Dunfield has given me permission to distribute these, but since he holds the license I cannot post it as a public project.

Download a tarball with sources and instructions here:

https://www.dropbox.com/sh/actw3a8k061uupq/AACFr6iC6L2x7_1gY5cbtVPfa?dl=0

If you want to do any bugfixing or enhancement, there's a Git bundle to get you setup with local repository.

It would be optimal if Dave would post this on the IMD web page, but he does not appear to have any interest in doing so (I've sent him the files).
 
You must log in or register to reply here.
Back
Top