Subject: Re: Trouble with CROSSWORKS on my new emachine From: WKRP Newsgroups: comp.sys.apple2 Date: Sat, 30 Sep 2000 18:48:29 -0400 Organization: The Internet Access Company, Inc. Lines: 45 Message-ID: <39D66DBD.9E173233@tiac.net> References: <39D553CC.249D829A@tiac.net> NNTP-Posting-Host: ip42.cambridge2.ma.pub-ip.psi.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.61 [en]C-CCK-MCD (Win98; U) X-Accept-Language: en Problem solved.. Some nice guy on another newsgroup (Yep, I crosspost when I'm desperate) told me to check the computers BIOS settings, and COM1 was set for "automatic". Per his advice I put in the address & IRQ I found in the Win98 Device Manager and the damn thing worked. I found I couldn't get CROSSWORKS to work in a DOS window under Win98, the file transfers kept aborting with checksum errors, but it worked "slicker than snot" when I started the machine in MSDOS mode. The second part of my post ("can't find the C drive") was solved when folks educated me about FAT32 vs FAT 16...You can't boot a PC which used FAT32 from any 10 year old MSDOS startup disk which dosen't know about FAT32. Jeff Wisnia W1BSV MIT '57 ee WKRP wrote: > I've used CROSSWORKS for years to transfer stuff from old Apple disks to > PCs. Recently I switched to a new emachine 533id2 tower running Win98. > When I tried to run CROSSWORKS on it the program seemed OK, but it > couldn't find the COM port. It reported "No serial port hardware found". > I was running MSDOS under Win98 and when in Win98 the serial driver was > reported installed and set to 19200 baud. Seems almost like the serial > driver gets turned off when I go to an MSDOS program. I tried booting > from an MSDOS disk. The boot went OK, but still the same problem. (In > addition, MSDOS couldn't find the hard drive???...Oh well...) > > Whadda I do guys? > > email copies of replies appreciated, my ISP's newew server is flakey > some days. > > Thanks, > > -- > > Jeff Wisnia W1BSV MIT '57 ee --