OS says win 98 but is NT

Status
Not open for further replies.
Hi all, Am ready to smash this PC. :knock: Have been to other tech forums, and told outrageous things. This was a 95 PC, then upgraded to 98SE. Have done everything can think of to get rid of NT. PC had crashed and a tech put a new motherboard on here. Things started acting up, and got process viewer and hijack this. Explorer is Win NT. I have reformatted c: drive which is 13 gig. Reinstalled 98. Have used Partition Magic and Fdisk to try and get rid of these partitions the tech made. And it still reverts back to nt. Had to use recover on my other drive 40 gig. Have so many duplicate files, have to sort them out. Anyway, now when I boot up, windows keeps saying I have to scan disk. In system are all the PCI devices listed with the ? on them.

No matter what the autoexec.bat which I have edited keeps coming back.

Couple of the 40 gig drive partions are FAT32X? Don't know what this is. Or Large drive placeholders. And were network drives. Have used partition deleters, etc etc. Every program I can find.

This is a home computer. And I don't want NT. Found several txt files RE: emulators, the guy put 95 on here first, then Y2K. Whatever he used also had a few trojans. Also found hotfixes. Hidden partitions.. So much. To top it off the place is out of business. Pay for a router, and backups on CD, and am out the money. I can't fdisk the 40, use pmagic. Nothing. Don't want to lose what programs I do have. Have 2 cd roms one a RW. Which won't work. My modem won't even be detected. Has been so long since had to fdisk and put partitions on a second drive to work with the main OS, Forgot how and what kind of partitions to make on the second drive. I HATE WINDOZE! Any help will be greatly appreciated. BTW: had gone into regedit and got rid of the nts, W2K. Went looking for the dlls pertaining to nt. dlls were renamed. Cab files, etc. Used DOS, and windows. Keep rescanning for virii and spyware. Nothing now. Will post the drive info, etc if anyone needs it to help. Miss the good old days when windoze wasn't even released. Built PC's, programmed. :bounce:

Autoexec.bat.
SET BLASTER=A220 I7 D1 H7 P320 T6
SET SBPCI=C:\AUDIOPCI

Thanks.....
 
I am assuming from your post that you have a windows nt partition on your system.. is that correct or am i reading it incorrectly

when you did fdisk did you run the fdisk /mbr switch to clear master boot record...

also when you ran fdisk (bear with me its been awhile.) if you choose option 4 to display partitions what partitions do you have listed there... Please respond with all partitions listed including partition size, format, Volume Label, and Which partition is the active partition.

Did you also try doing the option to delete partion then choose the option to delete non dos partitions.. because an ntfs partition is not a dos partition.. also when you went to fdisk did you choose yes to enabling large disk support?

worse case.... what brand is the hard drive.. western digital, maxtor, IBM, etc.. Go to their website and download their disk util tools. they shoud have a program that will zero the drive which will wipe everything from the disk.
 
urban,
TY so much for the quick response..... I believe they are NT Partititions. I used a program that was suppose to replace the MBR before formatting. Didn't have PMagic available to view in detail the MBR and FAT details. And now the C drive is 32X ..DARN. I had found a program that supposedly would tell if partions were NTFS. and it said no NTFS. So I don't know. They are Maxtor drives. Have been to the site.

I have the disk that came with the drive, that does a low level format. But, don't want to do that. Been in the Bios and Cmos so much, trying to see if something was set there also. Finally got a copy printed out ..txt.. of the mess I have now. When formatted C I used the format /s

So should I reformat AGAIN and use format C:/ mbr
That puts the system on it so it is bootable? Haven't really worked on these new systems. Keeps saying I have to shorten this..
===================================================
C:SEE FAT32X Pri,Boot 12,982.2 0 0 63 26,587,512
D: FAT32X Pri 9,773.9 0 0 63 20,016,927
ExtendedX Pri 29,306.1 0 1
E:NO NAME FAT32 Log
EPBR F:NO NAME FAT32 Log 9,671.9 40,435,605 0 40,435,668 19,808,082
Warning #113: EPBR partition starting at 60243750 overlaps previous EPBR partition.
G:NO NAME FAT32 Log 9,664.1 60,243,750 0 60,243,813 19,792,017
Boot Record for drive C: (Drive: 1, Starting sector: 63, Type: FAT32)
14. Big Total Sectors: 20016916 (0x1316F14)
15. Big Sectors per FAT: 9770
27. File System Type: FAT32
Boot Record for drive E: (Drive: 2, Starting sector: 20,017,053, Type: FAT32)
27. File System Type: FAT32
Boot Record for drive F: (Drive: 2, Starting sector: 40,435,668, Type: FAT32)
3. Bytes per Sector: 512
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 40435668 (0x268FFD4)
14. Big Total Sectors: 19808082 (0x12E3F52)
15. Big Sectors per FAT: 9668
18. First Cluster of Root: 2 (0x2)
27. File System Type: FAT32
Boot Record for drive G: (Drive: 2, Starting sector: 60,243,813, Type: FAT32)
4. Sectors per Cluster: 16
5. Reserved Sectors: 32
6. Number of FAT's: 2
Sectors per FAT: 9660
18. First Cluster of Root: 2 (0x2)
File System Type: FAT32
General System Information:
Current Page File Size: (bytes): 167,747,584
Disk Geometry Information for Disk 1: 1655 Cylinders, 255 Heads, 63 Sectors/Track
System PartSect # Boot BCyl Head Sect FS ECyl Head Sect StartSect NumSects
Disk Geometry Information for Disk 2: 4982 Cylinders, 255 Heads, 63 Sectors/Track
System PartSect # Boot BCyl Head Sect FS ECyl Head Sect StartSect NumSects
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 0 00 0 1 1 0C 1245 254 63 63 20016927
0 1 00 1022 0 1 0F 1022 254 63 20,016,990 60,018,840
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 1 00 1246 0 1 0F 4981 254 63 20016990 60018840
NO NAME 20,016,990 0 00 1022 1 1 0B 1022 254 63 20,017,053 20,418,552
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
20016990 0 00 1246 1 1 0B 2516 254 63 20017053 20418552
20,016,990 1 00 1022 0 1 05 1022 254 63 40,435,605 39,600,225
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
20016990 1 00 2517 0 1 05 4981 254 63 40435605 39600225
NO NAME 40,435,605 0 00 1022 1 1 0B 1022 254 63 40,435,668 19,808,082
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
40435605 0 00 2517 1 1 0B 3749 254 63 40435668 19808082
40,435,605 1 00 1022 0 1 05 1022 254 63 60,243,750 19,792,080
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
40435605 1 00 3750 0 1 05 4981 254 63 60243750 19792080
NO NAME 60,243,750 0 00 1022 1 1 0B 1022 254 63 60,243,813 19,792,017
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
60243750 0 00 3750 1 1 0B 4981 254 63 60243813 19792017
Partition Information for Disk 1: 12,982.2 Megabytes
Volume PartType Status Size MB PartSect # StartSect TotalSects
C:SEE FAT32X Pri,Boot 12,982.2 0 0 63 26,587,512
Partition Information for Disk 2: 39,080.0 Megabytes
Volume PartType Status Size MB PartSect # StartSect TotalSects
D: FAT32X Pri 9,773.9 0 0 63 20,016,927
ExtendedX Pri 29,306.1 0 1 20,016,990 60,018,840
EPBR Log 9,970.0 None -- 20,016,990 20,418,615
E:NO NAME FAT32 Log 9,970.0 20,016,990 0 20,017,053 20,418,552
EPBR Log 19,336.0 20,016,990 1 40,435,605 39,600,225
F:NO NAME FAT32 Log 9,671.9 40,435,605 0 40,435,668 19,808,082
EPBR Log 9,664.1 40,435,605 1 60,243,750 19,792,080
Warning #113: EPBR partition starting at 60243750 overlaps previous EPBR partition.
G:NO NAME FAT32 Log 9,664.1 60,243,750 0 60,243,813 19,792,017
Boot Record for drive C: (Drive: 1, Starting sector: 63, Type: FAT32)
2. OEM Name: MSWIN4.1
3. Bytes per Sector: 512
4. Sectors per Cluster: 16
5. Reserved Sectors: 32
6. Number of FAT's: 2
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 63 (0x3F)
14. Big Total Sectors: 26587512 (0x195B178)
15. Big Sectors per FAT: 12976
16. Extended Flags: 0x0000
17. FS Version: 0
18. First Cluster of Root: 2 (0x2)
19. FS Info Sector: 1
20. Backup Boot Sector: 6
Boot Record for drive D: (Drive: 2, Starting sector: 63, Type: FAT32)
1. Jump: EB 58 90
2. OEM Name: MSWIN4.1
3. Bytes per Sector: 512
4. Sectors per Cluster: 16
5. Reserved Sectors: 32
6. Number of FAT's: 2
7. Reserved: 0x0000
8. Reserved: 0x0000
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 63 (0x3F)
14. Big Total Sectors: 20016916 (0x1316F14)
15. Big Sectors per FAT: 9770
16. Extended Flags: 0x0000
17. FS Version: 0
18. First Cluster of Root: 19833 (0x4D79)
19. FS Info Sector: 1
20. Backup Boot Sector: 6
27. File System Type: FAT32
Boot Record for drive E: (Drive: 2, Starting sector: 20,017,053, Type: FAT32)
1. Jump: EB 58 90
2. OEM Name: MSWIN4.1
3. Bytes per Sector: 512
4. Sectors per Cluster: 16
5. Reserved Sectors: 32
6. Number of FAT's: 2
9. Media Descriptor: 0xF8
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 20017053 (0x1316F9D)
14. Big Total Sectors: 20418552 (0x1378FF8)
15. Big Sectors per FAT: 9966
16. Extended Flags: 0x0000
17. FS Version: 0
18. First Cluster of Root: 2 (0x2)
20. Backup Boot Sector: 6
27. File System Type: FAT32
Boot Record for drive F: (Drive: 2, Starting sector: 40,435,668, Type: FAT32)
2. OEM Name: MSWIN4.1
3. Bytes per Sector: 512
4. Sectors per Cluster: 16
5. Reserved Sectors: 32
6. Number of FAT's: 2
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 40435668 (0x268FFD4)
14. Big Total Sectors: 19808082 (0x12E3F52)
15. Big Sectors per FAT: 9668
16. Extended Flags: 0x0000
17. FS Version: 0
18. First Cluster of Root: 2 (0x2)
19. FS Info Sector: 1
20. Backup Boot Sector: 6
21. Reserved: 000000000000000000000000
22. Drive ID: 0x80
27. File System Type: FAT32
28. Boot Signature: 0xAA55
Boot Record for drive G: (Drive: 2, Starting sector: 60,243,813, Type: FAT32)
1. Jump: EB 58 90
2. OEM Name: MSWIN4.1
3. Bytes per Sector: 512
4. Sectors per Cluster: 16
5. Reserved Sectors: 32
6. Number of FAT's: 2
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 60243813 (0x3973F65)
14. Big Total Sectors: 19792017 (0x12E0091)
15. Big Sectors per FAT: 9660
18. First Cluster of Root: 2 (0x2)
20. Backup Boot Sector: 6
27. File System Type: FAT32
 
Is one of the devices connected via usb or possibly PCI/ISA slot?
___________________

With this new Tyan motherboard, something is PCI, he wouldn't tell me. Have all those PCI things in the system with the ? marks. Grrrrrrrrrr. Guess will go back into the bios. If one of the devices is, what then? :bounce:
___________________________________
from what i have found FAT32X may relate to X10 Devices. you can look here, this is for windows xp but still seems to be about the same.
_____________________
Thanks for the URL. Now what the heck is an X10 device LOL.
_____________________________
http://www.samsungpc.com/products/x..._faqanswer9.htm
_______________________________________
oh and i think the command you are looking for is "format (driveLetter /s"
to copy the system files to the newly formatted partition
_________________________
Yep, that is the command I used when I formatted C:
Will have to read more on that URL... Just love it when techs won't tell you things, what is what. Grrr. He did this all in a day. So think he used the same procedure on a few other PC's. No wonder they are out of business. Wherever he got the programs, and they had a trojan dropper. Which might be part of the mess I have had.

I still don't understand the reason for the autoexec.bat being
SET BLASTER=A220 I7 D1 H7 P320 T6
SET SBPCI=C:\AUDIOPCI
So has to be PCI involved somewhere.
I hate all this newfangled stuff. Thanks so much. Know the owners name of the place. Now if could only get that techs name. He calls himself a Tech. Sheesh. He needs to be :knock: on the head.
 
still don't understand the reason for the autoexec.bat being
SET BLASTER=A220 I7 D1 H7 P320 T6
SET SBPCI=C:\AUDIOPCI


Its been a while since configuring hardware using autoexec.bat and config.sys but from what i can remember it looks like the settings above are for a sound card.

X10... X10 from what i have read on it is a means of controlling external devices with your computer. such as having a light switch hooked up that is set to turn on at a specific time... there are many x10 type devices.. i am betting that if you do not know what it is you probably dont have one in your system.


that article also gave a way of resolving the problem but it may or may not work. it looked similar to what i had posted earlier as well.
 
Urban,

still don't understand the reason for the autoexec.bat being
SET BLASTER=A220 I7 D1 H7 P320 T6
SET SBPCI=C:\AUDIOPCI
____________________________________________
Came across this about the autoexec.bat:
SET BLASTER=A220 I7 D1 H7 P330 T6
SET SBPCI=C:\AUDIOPCI
@if exist c:\checkmbr.exe c:\checkmbr quiet (Validate MBR, not a TSR)
REM System Commander placeholder - A file should be present for file REM management. Do not delete file, but file replacement or editing OK. set TNS_NAMES=c:\ora817\network\admin
set path=c:\OraDev\jdk\bin;"C:\ProgramFiles\Oracle\jre\1.1.7\bin";
set Path=c:\Ora817\bin;"%Path%"
PATH c:\OraDev\bin;"%PATH%"

Interesting!
Will look for Oracle etc to see if anything is discovered.
Have read up of gdisk, and are more con articles than Pro.
I did manage to get it, and it hasn't done anything for me.
________________________________
Its been a while since configuring hardware using autoexec.bat and config.sys but from what i can remember it looks like the settings above are for a sound card.
_____________________
Is exactly what I thought!!
_____________________________________
X10... X10 from what i have read on it is a means of controlling external devices with your computer. such as having a light switch hooked up that is set to turn on at a specific time... there are many x10 type devices.. i am betting that if you do not know what it is you probably dont have one in your system.
____________
Yep, xactly
_______________________
that article also gave a way of resolving the problem but it may or may not work. it looked similar to what i had posted earlier as well.
______________________________
The info was great. TY. Why microsoft ever had to incorporate win 32 and 32X, Y2K, ME, XPPro into OS I will never know. Ran ole 95 16 bit for several years with no problem. GDisk is more $$ for microsoft. Have my 386 with 2 drives, 800 meg and 400 meg <think it is> Dos 3.11 for 15 years now and is still humming along. No PC's today will IMHO will last that long. Thank you again so much. Thought the above about SET BLASTER=A220 I7 D1 H7 P330 T6
SET SBPCI=C:\AUDIOPCI
@if exist c:\checkmbr.exe c:\checkmbr quiet (Validate MBR, not a TSR)
REM System Commander placeholder - A file should be present for file
REM management. Do not delete file, but file replacement or editing OK.
set TNS_NAMES=c:\ora817\network\admin
set path=c:\OraDev\jdk\bin;"C:\ProgramFiles\Oracle\jre\1.1.7\bin";
set Path=c:\Ora817\bin;"%Path%"
PATH c:\OraDev\bin;"%PATH%" was very ....interesting. Has nothing to do with the sound card. As I set this OS up without it, before it mysteriously appeared again. Going to check out the MBR. Never saw a MBR.exe before.

Thanks again............
 
This is easily the most convoluted, incomprehensible thread I have ever seen.

If there are 2 harddisks in that PC (if not, put a second one in), copy anything you want to safe onto that 2nd disk.
Then go to the 'bad' HD manufacturers website and get their zerofill utility.
This will wipe out EVERYTHING on that PC, all partitions, data etc.
or try AEFDISK from http://www.aefdisk.com/

Those SET BLASTER etc. lines are from the DOS-version of Creative Soundblaster. They only appear in W95/W98.
 
Hi Real,
>This is easily the most convoluted, incomprehensible >thread I have ever seen.
___________________________________
:giddy: I have to chuckle at the above comment. Yes I agree with you.
______________________
>If there are 2 harddisks in that PC (if not, put a second >one in), copy anything you want to safe onto that 2nd >disk.Then go to the 'bad' HD manufacturers website and >get their zerofill utility. This will wipe out EVERYTHING on >that PC, all partitions, data etc. or try AEFDISK from >http://www.aefdisk.com/
_______________________
There are 2 hard disks. Was confirmed the place went bankrupt. Propably sued. Found the motherboard driver CD. It does support 98 some, BUT the drivers that were used were for Y2K and NT. Uses mainly PCI peripherals. Another PC place, called them and the guy was telling me that Tyan is used MAINLY for networking with NT. Was telling him all the things that I found on the PC and differerent drivers for the board need to be installed. The other guy renamed files, extensions. The below blaster commands are embedded in the chipset. <from what I gather> Is why the autoexec.bat though empty when start out, reappears. NT is installed on here Real. Found driver for Blaster on Tyan's website. All these drivers, chipsets is enough to drive one batty. At least I know I wasn't wrong in all that is happening. :confused: <confirmed> TY for the website. :) Will pass that one on the the others I have been helping with PC's.Gdisk didn't work. So the fun begins AGAIN!
_________________________
>Those SET BLASTER etc. lines are from the DOS-version >of Creative Soundblaster. They only appear in W95/W98.
_____________________
If I don't suceed, will have to call the guy and have him get PC. Thank heavens no charge for them to pick it up.
A lot of troubleshooting is in the agenda. So glad I found this forum. Least not called nutso.

Thank you so much........... wonder how many other people's probs aren't because of sneaky techs.
 
No offense meant, but your answer is as bad as the rest of the post.
Nothing of it makes sense.
Booting from a W98 floppy should let you FDISK & FORMAT any HD.

I'll move this to the Storage forum.
 
Status
Not open for further replies.
Back