Re: How to enable USB drives in both Windows 98SE AND MS-DOS 7.1.

[Curious Marc via cctalk]

Here you go: 

Networking between Win98 and Win7

On Windows 7, using regedit, set

“HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\LMCompatibilityLevel” 
to “1”
You might need to create the new entry under \lsa as a REG_DWORD, set 
to 1

On the Win98 machine:
You have to install the Active Directory Extension, part of
the unofficial service pack 3 which you have to download
It's the first option on the install. I installed just that.

Then from there it's regular stuff: put the machines on the same workgroup 
name, enable sharing of your folders, permissions, etc...
  
From Win7, the Win98 machine appears in the Network, just click on it to browse 
the shares

From Win98, Win7 is not accessible from the Network Neighborhood. You have to 
type
directly the share address in an Explorer toolbar window like so
\\Workshop\SharedFolder
I had to shorten my share names for this to work, long names did not 
work.
Marc

> On Feb 7, 2018, at 3:37 PM, Terry Stewart via cctalk  
> wrote:
> 
>> On Thu, Feb 8, 2018 at 9:28 AM, Curious Marc  wrote:
>> 
>> Thanks Terry, I need to get my DOS7.1/Win98 Dolch to speak USB, that will
>> be helpful, particularly the DOS portion. I got my Win98 networked to Win7,
>> it's not that hard *once you know* and works really well. You have to
>> change one entry in the Win7 registry and add one package from the
>> unofficial Win98 service pack. If I find my notes I'll post them here.
>> Marc
>> 
> 
> Thanks Marc,
> 
> I probably won't attempt networking again (I did once), as I don't have a
> crossover cable and it's very convenient just to use the flash drive.  It
> would be good to know how to do it though and I'm sure other would
> appreciate that info.
> 
> Cheers
> 
> Terry
> 
>> 
>> 

Re: anybody need a 25 foot Unibus cable?

[Zane Healy via cctalk]

> On Feb 7, 2018, at 9:46 PM, Jon Elson via cctalk  
> wrote:
> 
> While cleaning up at work, I found a 25 foot Unibus cable in decent 
> condition.  Anybody need one?
> 
> Jon

I wish I needed one, that would be an interesting problem to have. :-)

Actually you jogged a memory, I think I have something like that out in the 
garage in with my PDP-11 spares.

Zane

anybody need a 25 foot Unibus cable?

[Jon Elson via cctalk]

While cleaning up at work, I found a 25 foot Unibus cable in 
decent condition.  Anybody need one?


Jon

Re: How to enable USB drives in both Windows 98SE AND MS-DOS 7.1.

[Mike Stein via cctalk]

Back in the W98SE days I bought USB sticks that came with drivers, so W98 has 
never been a problem.

Another approach for DOS if the system has 'boot from USB' capability is to 
just make a bootable DOS7 USB stick. 
Stick in: DOS, stick out: WIN98/XP/VISTA etc.; transfer files to heart's 
content.

Excellent writeup; thanks, Tez!

m

- Original Message - 
From: "Terry Stewart via cctalk" 
To: "Grant Taylor" ; "General Discussion: 
On-Topic and Off-Topic Posts" 
Sent: Wednesday, February 07, 2018 11:14 PM
Subject: Re: How to enable USB drives in both Windows 98SE AND MS-DOS 7.1.


>I thought there were alternate config.sys and autoexec.bat files that
were used if you chose to reboot to MS-DOS mode, and possibly if you hit F8
and chose command line during boot.

Yes, the files you speak of are config.dos and autoexec.dos.  These
confused me at first because I thought just as you did. I put the driver
files in there. However, those files seem to be associated with the
PREVIOUS MS-DOS version (if one exists) prior to installation of Windows
98, NOT the CLI of Windows 98 (MS-DOS 7.1).  There is an option when
starting Windows 98 to boot to an earlier version of MS-DOS.  If this
earlier version is selected, then config.dos and autoexec.dos are read and
processed as config.sys and autoexec.bat for the DOS boot.  Otherwise, if
booting the Windows 98 (MS-DOS 7.1) CLI, these files are ignored and only
autoexec.bat and config.sys (if they exist) are processed.

Initially, I thought booting to the previous DOS install (in my case MS-DOS
6.2) would solve the USB problem, and I simply called up the older DOS
(MS-DOS 6.2) with the drivers using those *.dos files.  However, I was then
crippled by only being able to use a USB drive with FAT16 and a small
capacity.  I needed an MS-DOS 7.1 environment to give me FAT 32 hence the
config.sys "menu" system.

Terry (Tez)









On Thu, Feb 8, 2018 at 4:20 PM, Grant Taylor via cctalk <
cctalk@classiccmp.org> wrote:

> On 02/06/2018 12:58 PM, Terry Stewart via cctalk wrote:
>
>> The title might suggest to topic is not vintage, but the reason I did
>> this myself was to facilitate classic computer disk imaging.
>>
>
> I'd think that something from ~20 years ago is indeed vintage.  (It's
> closer to the 25 year old requirement for cards to be vintage, than not.)
> Just not quite as vintage as some of the other topics on cctalk.
>
> I’ve recently given USB drive capability to the MS-DOS 7.1 environment in
>> a Windows 98SE computer I use for the purpose above. It was a bit of work
>> configuring the machine to ensure both the MS-DOS drivers and the Windows
>> 98SE drivers co-existed peacefully.
>>
>
> Intriguing.
>
> I figured that such was possible, but I've never tried.
>
> I'm no  Windows 98 guru (or MS-DOS guru for that matter) so it may not be
>> the most efficient or elegant of solutions.   However, it worked for me.
>> That being the case I thought I’d document what I did.
>>
>
> I thought there were alternate config.sys and autoexec.bat files that were
> used if you chose to reboot to MS-DOS mode, and possibly if you hit F8 and
> chose command line during boot.
>
> Quick Google searches make me think that the MS-DOS mode files are named
> config.dos and autoexec.dos.  Then Windows will rename them when you select
> reboot into MS-DOS mode.
>
> Hopefully the article will be useful to others who might want to do this.
>>
>> http://www.classic-computers.org.nz/blog/2018-02-05-USB-in-M
>> S-DOS-and-Win98.htm
>>
>
> Thank you for sharing.
>
> I'm filing that away for future use.
>
>
>
> --
> Grant. . . .
> unix || die
>

Re: How to enable USB drives in both Windows 98SE AND MS-DOS 7.1.

[Mike Stein via cctalk]

Having trouble with that link; any tips?

m

- Original Message - 
From: "Grant Taylor via cctalk" 
To: 
Sent: Wednesday, February 07, 2018 11:58 PM
Subject: Re: How to enable USB drives in both Windows 98SE AND MS-DOS 7.1.


> On 02/07/2018 09:53 PM, Grant Taylor via cctalk wrote:
>> According to the following link from IBM, the process we are both 
>> thinking of is valid, just using different files.
>> 
>> http://ps-2.kev009.com/pcpartnerinfo/ctstips/c546.htm
> 
> That link mentions ExittoDOS.pif, and searches for it turn up related 
> information about dosstart.bat.
> 
> I'd suggest digging around for them and some web searches.
> 
> I don't currently have a 9x (V)M to test things on.
> 
> 
> 
> -- 
> Grant. . . .
> unix || die

Re: How to enable USB drives in both Windows 98SE AND MS-DOS 7.1.

[Grant Taylor via cctalk]

On 02/07/2018 09:53 PM, Grant Taylor via cctalk wrote:
According to the following link from IBM, the process we are both 
thinking of is valid, just using different files.


http://ps-2.kev009.com/pcpartnerinfo/ctstips/c546.htm


That link mentions ExittoDOS.pif, and searches for it turn up related 
information about dosstart.bat.


I'd suggest digging around for them and some web searches.

I don't currently have a 9x (V)M to test things on.



--
Grant. . . .
unix || die

Re: How to enable USB drives in both Windows 98SE AND MS-DOS 7.1.

[Grant Taylor via cctalk]

On 02/07/2018 09:14 PM, Terry Stewart wrote:
Yes, the files you speak of are config.dos and autoexec.dos.  These 
confused me at first because I thought just as you did. I put the driver 
files in there. However, those files seem to be associated with the 
PREVIOUS MS-DOS version (if one exists) prior to installation of Windows 
98, NOT the CLI of Windows 98 (MS-DOS 7.1).  There is an option when 
starting Windows 98 to boot to an earlier version of MS-DOS.  If this 
earlier version is selected, then config.dos and autoexec.dos are read 
and processed as config.sys and autoexec.bat for the DOS boot.  
Otherwise, if booting the Windows 98 (MS-DOS 7.1) CLI, these files are 
ignored and only autoexec.bat and config.sys (if they exist) are processed.


According to the following link from IBM, the process we are both 
thinking of is valid, just using different files.


http://ps-2.kev009.com/pcpartnerinfo/ctstips/c546.htm

Initially, I thought booting to the previous DOS install (in my case 
MS-DOS 6.2) would solve the USB problem, and I simply called up the 
older DOS (MS-DOS 6.2) with the drivers using those *.dos files.  
However, I was then crippled by only being able to use a USB drive with 
FAT16 and a small capacity.  I needed an MS-DOS 7.1 environment to give 
me FAT 32 hence the config.sys "menu" system.


Ya.  MS-DOS < 7.x doesn't understand FAT-32 drives.  -  I think there 
are drivers that you can load to add support for it.  Or you can just 
use MSDOS.SYS, IO.SYS, and COMMAND.COM from Windows 9x.




--
Grant. . . .
unix || die

Re: How to enable USB drives in both Windows 98SE AND MS-DOS 7.1.

[Chuck Guzis via cctalk]

I recall using these drivers several years ago.

As I recall, the problem is that they're not amenable to hot-swapping.
That is, is you're using a USB flash drive with them, there was no code
that allowed you to remove the drive and substitute another without
rebooting.

Has this situation changed?

On a related note, I have several Ralink RT5370 USB Wifi dongles that I
find to be quite useful.

Has anyone gotten one to work with Windows 98SE (I won't even bring up
MS-DOS)?

I wondered if I could find a Windows 2000 miniport driver for it, that
it might work in Windows 98.

--Chuck

Re: How to enable USB drives in both Windows 98SE AND MS-DOS 7.1.

[Terry Stewart via cctalk]

 >I thought there were alternate config.sys and autoexec.bat files that
were used if you chose to reboot to MS-DOS mode, and possibly if you hit F8
and chose command line during boot.

Yes, the files you speak of are config.dos and autoexec.dos.  These
confused me at first because I thought just as you did. I put the driver
files in there. However, those files seem to be associated with the
PREVIOUS MS-DOS version (if one exists) prior to installation of Windows
98, NOT the CLI of Windows 98 (MS-DOS 7.1).  There is an option when
starting Windows 98 to boot to an earlier version of MS-DOS.  If this
earlier version is selected, then config.dos and autoexec.dos are read and
processed as config.sys and autoexec.bat for the DOS boot.  Otherwise, if
booting the Windows 98 (MS-DOS 7.1) CLI, these files are ignored and only
autoexec.bat and config.sys (if they exist) are processed.

Initially, I thought booting to the previous DOS install (in my case MS-DOS
6.2) would solve the USB problem, and I simply called up the older DOS
(MS-DOS 6.2) with the drivers using those *.dos files.  However, I was then
crippled by only being able to use a USB drive with FAT16 and a small
capacity.  I needed an MS-DOS 7.1 environment to give me FAT 32 hence the
config.sys "menu" system.

Terry (Tez)









On Thu, Feb 8, 2018 at 4:20 PM, Grant Taylor via cctalk <
cctalk@classiccmp.org> wrote:

> On 02/06/2018 12:58 PM, Terry Stewart via cctalk wrote:
>
>> The title might suggest to topic is not vintage, but the reason I did
>> this myself was to facilitate classic computer disk imaging.
>>
>
> I'd think that something from ~20 years ago is indeed vintage.  (It's
> closer to the 25 year old requirement for cards to be vintage, than not.)
> Just not quite as vintage as some of the other topics on cctalk.
>
> I’ve recently given USB drive capability to the MS-DOS 7.1 environment in
>> a Windows 98SE computer I use for the purpose above. It was a bit of work
>> configuring the machine to ensure both the MS-DOS drivers and the Windows
>> 98SE drivers co-existed peacefully.
>>
>
> Intriguing.
>
> I figured that such was possible, but I've never tried.
>
> I'm no  Windows 98 guru (or MS-DOS guru for that matter) so it may not be
>> the most efficient or elegant of solutions.   However, it worked for me.
>> That being the case I thought I’d document what I did.
>>
>
> I thought there were alternate config.sys and autoexec.bat files that were
> used if you chose to reboot to MS-DOS mode, and possibly if you hit F8 and
> chose command line during boot.
>
> Quick Google searches make me think that the MS-DOS mode files are named
> config.dos and autoexec.dos.  Then Windows will rename them when you select
> reboot into MS-DOS mode.
>
> Hopefully the article will be useful to others who might want to do this.
>>
>> http://www.classic-computers.org.nz/blog/2018-02-05-USB-in-M
>> S-DOS-and-Win98.htm
>>
>
> Thank you for sharing.
>
> I'm filing that away for future use.
>
>
>
> --
> Grant. . . .
> unix || die
>

Re: OpenVMS software repositories?

[Zane Healy via cctalk]

> On Feb 7, 2018, at 7:22 PM, Grant Taylor via cctalk  
> wrote:
> 
> On 02/07/2018 06:35 PM, Zane Healy via cctalk wrote:
>> What sites still exist that have VMS software?  I know the about the OpenVMS 
>> Freeware CD’s from HP VMS Engineering.
> 
> I'd suggest that you redirect your question to the comp.os.vms newsgroup.  I 
> frequently see discussions there about software archives. In fact, you can 
> probably search an archive of the group and find some answers to your 
> question.

I need to see about getting back on comp.os.vms, I’ve not been active there in 
a decade.

Zane

Re: OpenVMS software repositories?

[Zane Healy via cctalk]

> On Feb 7, 2018, at 7:05 PM, Carlos E Murillo-Sanchez 
>  wrote:
> 
> Zane Healy via cctalk wrote:
>> What sites still exist that have VMS software?  I know the about the OpenVMS 
>> Freeware CD’s from HP VMS Engineering.
>> 
>> http://h41379.www4.hpe.com/openvms/freeware/collections.html
>> 
>> As an example, I’ve found part of the old DECwindows archive, but it looks 
>> like that site is basically gone.
>> 
> Probably not what you are looking for, but these are handy:
> 
> http://nchrem.tnw.tudelft.nl/openvms/software2.html
> http://de.openvms.org/OpenVMS-Ports/list.php?by=Category
> 
> carlos.
> 

WOW!!!  That first one is quite impressive, though it’s a shame they aren’t 
offering binaries.

The second one looks most promising.  I’ll have to see about getting SQLite3 
running on my VAX and Alpha systems, as that might be the answer to my one 
problem.

This actually makes me want an Itanium system.

Zane

Re: OpenVMS software repositories?

[Grant Taylor via cctalk]

On 02/07/2018 06:35 PM, Zane Healy via cctalk wrote:
What sites still exist that have VMS software?  I know the about the 
OpenVMS Freeware CD’s from HP VMS Engineering.


I'd suggest that you redirect your question to the comp.os.vms 
newsgroup.  I frequently see discussions there about software archives. 
In fact, you can probably search an archive of the group and find some 
answers to your question.




--
Grant. . . .
unix || die

Re: OpenVMS software repositories?

[Carlos E Murillo-Sanchez via cctalk]

Zane Healy via cctalk wrote:

What sites still exist that have VMS software?  I know the about the OpenVMS 
Freeware CD’s from HP VMS Engineering.

http://h41379.www4.hpe.com/openvms/freeware/collections.html

As an example, I’ve found part of the old DECwindows archive, but it looks like 
that site is basically gone.


Probably not what you are looking for, but these are handy:

http://nchrem.tnw.tudelft.nl/openvms/software2.html
http://de.openvms.org/OpenVMS-Ports/list.php?by=Category

carlos.

OpenVMS software repositories?

[Zane Healy via cctalk]

What sites still exist that have VMS software?  I know the about the OpenVMS 
Freeware CD’s from HP VMS Engineering.  

http://h41379.www4.hpe.com/openvms/freeware/collections.html

As an example, I’ve found part of the old DECwindows archive, but it looks like 
that site is basically gone.

Zane

Re: How to enable USB drives in both Windows 98SE AND MS-DOS 7.1.

[Terry Stewart via cctalk]

On Thu, Feb 8, 2018 at 9:28 AM, Curious Marc  wrote:

> Thanks Terry, I need to get my DOS7.1/Win98 Dolch to speak USB, that will
> be helpful, particularly the DOS portion. I got my Win98 networked to Win7,
> it's not that hard *once you know* and works really well. You have to
> change one entry in the Win7 registry and add one package from the
> unofficial Win98 service pack. If I find my notes I'll post them here.
> Marc
>

 Thanks Marc,

I probably won't attempt networking again (I did once), as I don't have a
crossover cable and it's very convenient just to use the flash drive.  It
would be good to know how to do it though and I'm sure other would
appreciate that info.

Cheers

Terry

>
>

Re: Maxtor full-height 5.25" drives of death

[Ian Finder via cctalk]

> Drives of the day were power hungry and ran hot.  Heat is a killer.

Yes, certainly heat is why these drives go onto a shelf working and come
off of it broken with servo and head amplifier problems at an astonishing
rate far higher than their contemporary brethren.
It also helps answer my question of common failure modes- surely, it must
be the refrigeration on the drives that fails while it is on the shelf.
Perhaps the freon slowly leaks.

Thank you for this insightful response.

Re: Maxtor full-height 5.25" drives of death

[allison via cctalk]

On 2/7/18 2:36 PM, Ian Finder via cctalk wrote:

XT2190s, XT1140s, some of the early ESDI disks...
I have 6 XT2190s at home, and maybe one of the damn things works.

Does anyone out here know, beyond speculation, what some of the common
failure modes of these drives are? I'm not opposed to open-HDA surgery.

And I probably won't do anything.
But the question of WHY this line of drives in particular sucks so much has
haunted me for some time...


Drives of the day were power hungry and ran hot.  Heat is a killer.

I have a few that work but I got them  young and kept them cool
so they held up much better.  The trick was BA123 (large and roomy)
and an extra fan behind it.

Another drive was the SA250, kept cool the ran long but with poor airflow
maybe 16 months.

Allison

htly boxed with
- Ian

Honorable mention: CDC Sabre, Wren.

Maxtor full-height 5.25" drives of death

[Ian Finder via cctalk]

XT2190s, XT1140s, some of the early ESDI disks...
I have 6 XT2190s at home, and maybe one of the damn things works.

Does anyone out here know, beyond speculation, what some of the common
failure modes of these drives are? I'm not opposed to open-HDA surgery.

And I probably won't do anything.
But the question of WHY this line of drives in particular sucks so much has
haunted me for some time...

- Ian

Honorable mention: CDC Sabre, Wren.

-- 
   Ian Finder
   (206) 395-MIPS
   ian.fin...@gmail.com

Re: 8" floppy drives from AMD development system?

[Al Kossow via cctalk]

AMD made a whole Multibus product line covered in
http://bitsavers.org/pdf/amd/multibus

in particular AMD_Multibus_OEM_Products_May84.pdf

On 2/6/18 10:55 PM, Steven M Jones via cctalk wrote:
> Anybody notice this eBay auction? https://cgi.ebay.com/itm/222816138475
> 
> I'd guess it was part of a packaged AMD development system, maybe somebody 
> recalls some specifics...? 

Searching for EBBS][

[JP Hindin via cctalk]

As the title suggests, I'm looking for a copy of the EBBS][ software for a 
friend who used to run an Apple based BBS many moons ago and is looking 
out for a bit of nostalgia. So far he's been unable to locate the disks 
the system used to be on (he suspects damaged in a storage space flood in 
the late 90s) and my google fu is weak.


Would anyone be able to help us out here?

Replies should probably be kept off-list.

My thanks to all;

 - JP

Re: Google, Wikipedia directly on ASCII terminal?

[Christian Corti via cctalk]

On Tue, 6 Feb 2018, Grant Taylor wrote:
Watching Curious Marc's HP 264x Terminals - Part 3: Living the ASCII Life 
video made me think of this thread.


Check out Marc's did video about 17 minutes into the video.  The video shows 
Ken using the HP 264x terminal to run Lynx on a Linux box to access Google.


One needs a video for this? ;-)
That is one of the things we're doing casually for over 15 years here. May 
it be a VT100, a HP 2648 or even the VT52 emulation within the IBM 5110 
Kermit ;-)

(BTW all the equipment is connected to terminal servers)

Christian